Website Health & Uptime

Explore the latest status updates for Twitter

Recent Status Logs

272 ms
6/2/2025, 4:30:01 PM
2275 ms
6/2/2025, 4:00:01 PM
439 ms
6/2/2025, 3:30:01 PM
447 ms
6/2/2025, 3:00:01 PM
2295 ms
6/2/2025, 2:30:01 PM
434 ms
6/2/2025, 2:00:01 PM
401 ms
6/2/2025, 1:00:01 PM
362 ms
6/2/2025, 12:30:01 PM
236 ms
6/2/2025, 12:00:01 PM
412 ms
6/2/2025, 11:30:01 AM
327 ms
6/2/2025, 11:00:01 AM
242 ms
6/2/2025, 10:30:01 AM
292 ms
6/2/2025, 10:00:02 AM
308 ms
6/2/2025, 9:30:01 AM
395 ms
6/2/2025, 9:00:01 AM
293 ms
6/2/2025, 8:30:01 AM
489 ms
6/2/2025, 8:00:01 AM
279 ms
6/2/2025, 7:30:01 AM
391 ms
6/2/2025, 7:00:01 AM
478 ms
6/2/2025, 6:00:01 AM
298 ms
6/2/2025, 5:30:01 AM
595 ms
6/2/2025, 5:00:01 AM
406 ms
6/2/2025, 4:30:01 AM
572 ms
6/2/2025, 4:00:01 AM
235 ms
6/2/2025, 3:30:01 AM
1261 ms
6/2/2025, 3:00:01 AM
335 ms
6/2/2025, 2:30:01 AM
495 ms
6/2/2025, 1:00:01 AM
428 ms
6/2/2025, 12:30:01 AM
1254 ms
6/2/2025, 12:00:01 AM

Status Legend

OnlineFacing IssuesOffline

How does it work?

We check the status of a website by doing a HTTP GET request.

Depending on the status response of that request we determine if the site is online/offline or having issues

If the status response is in the 200 or 300 range then we determine the site is online

If the status response is in the 400 or 500 range then we determine the site might be having issues

Any other status, or a no response is determined as being offline

The number next to the icon of the status determines the number of milliseconds that it took to get an answer on the GET request.