What’s failing right now.
Most visited first
391 websites- Wikipediawikipedia.orgUp99.44%No failed checks131 ms avg
- Wikimedia Commonscommons.wikimedia.orgUp99.72%No failed checks117 ms avg
- Wiktionarywiktionary.orgUp99.58%No failed checks197 ms avg
- Internet Archivearchive.orgUp99.08%No failed checks650 ms avg
- Stack Exchangestackexchange.comUp98.85%No failed checks198 ms avg
- Wolfram Alphawolframalpha.comUp99.29%No failed checks1,054 ms avg
- Dictionary.comdictionary.comUp99.22%No failed checks119 ms avg
- Google Translatetranslate.google.comUp99.36%No failed checks226 ms avg
- DeepLdeepl.comUp99.36%No failed checks253 ms avg
- Google Mapsmaps.google.comUp99.58%No failed checks785 ms avg
- OpenStreetMapopenstreetmap.orgUp99.51%No failed checks168 ms avg
- Wazewaze.comUp99.36%No failed checks207 ms avg
- Amazon Web Servicesaws.amazon.comUp99.79%No failed checks186 ms avg
- Microsoft Azureazure.microsoft.comUp99.65%No failed checks3,519 ms avg
- Google Cloudcloud.google.comUp99.44%No failed checks118 ms avg
- Cloudflarecloudflare.comUp99.36%No failed checks122 ms avg
- DigitalOceandigitalocean.comUp99.44%No failed checks110 ms avg
- Hetznerhetzner.comUp99.22%No failed checks66 ms avg
- OVHcloudovhcloud.comUp99.01%No failed checks218 ms avg
- Fastlyfastly.comUp99.22%No failed checks411 ms avg
- Vercelvercel.comUp99.44%No failed checks118 ms avg
- Netlifynetlify.comUp99.29%No failed checks700 ms avg
- Renderrender.comUp99.65%No failed checks340 ms avg
- Railwayrailway.comUp99.57%No failed checks180 ms avg
No problemsSome checks failedMostly failingRestrictedNo dataResponse time, red where checks failedBars: 90 days · line: 24 hours in 15-minute steps · UTC · refreshes every minute
Independent checks from every monitoring location, keeping the fastest response. A step turns red only where no location got a successful response; that can still be a network problem on our side, so a single red step is not proof of an outage.