Skip to content

RealUptime Outages

Our check readings, with the vendor's own status beside them.

Check readings for 946 popular services, taken by our own probe fleet. A reading shows whether our check of a service passed, not whether it works for you. Free, no account.

Monitor your own servers the same way

For 320 of these 946 services we read the vendor's own status feed, and what the vendor reports leads. The sections headed “Our checks” cover the 626 whose feed we cannot read. Our regional reading of the others sits beside the vendor's statement on each service's page.

Vendor reports an incident10

RailwayVendor reports an incidentExternal network blocks affecting access to Railway · since 2026-11-04 18:54 UTC · as of the last successful poll, 2026-11-07 16:54 UTC · share: realuptime.io/outages/railwayCloudflareVendor reports an incidentSpectrum Availability Issue in Phoenix · since 2026-11-07 00:59 UTC · as of the last successful poll, 2026-11-07 17:04 UTC · share: realuptime.io/outages/cloudflareGcoreVendor reports an incidentAll Services | Singapore Incident Details · since 2026-11-07 06:34 UTC · as of the last successful poll, 2026-11-07 17:14 UTC · share: realuptime.io/outages/gcoreKrakenVendor reports an incidentBRL PIX Withdrawal Issues · since 2026-11-05 16:03 UTC · as of the last successful poll, 2026-11-07 17:24 UTC · share: realuptime.io/outages/krakenLightspeedVendor reports an incidentA possible delay for Nov 4 2026 payouts may be experienced by a subset of L & K series merchants · since 2026-11-05 18:01 UTC · as of the last successful poll, 2026-11-07 17:24 UTC · share: realuptime.io/outages/lightspeed-posScalewayVendor reports an incident[DEDIBOX] - RPNv1 network unavailability in DC3 room 4-4 corridors C and D · since 2026-11-06 15:20 UTC · as of the last successful poll, 2026-11-07 16:54 UTC · share: realuptime.io/outages/scalewaySinchVendor reports an incidentDelivery Issue - SMS Verification - China · since 2026-11-06 05:05 UTC · as of the last successful poll, 2026-11-07 17:14 UTC · share: realuptime.io/outages/sinchSourceHutVendor reports an incidentgit.sr.ht under high load · since 2026-11-05 15:00 UTC · as of the last successful poll, 2026-11-07 17:14 UTC · share: realuptime.io/outages/sourcehutTwilioVendor reports an incidentSMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Multiple Networks in New Zealand · since 2026-11-07 02:57 UTC · as of the last successful poll, 2026-11-07 17:04 UTC · share: realuptime.io/outages/twilioVendVendor reports an incidentA possible delay for Nov 4 2026 payouts may be experienced by a subset of L & K series merchants · since 2026-11-05 18:01 UTC · as of the last successful poll, 2026-11-07 17:24 UTC · share: realuptime.io/outages/vend-hq

Our checks failing now0

None of our checks are failing from two or more regions right now. This does not show every service is working.

Degraded1

SteamDegradedchecked moments ago · no vendor incident listed · share: realuptime.io/outages/steam

Checks passing625

Vendor lists an incident, no outage declared27

Vendor reports no incident283

The vendor's own pageTheir word for it
All systems operationalExample

A vendor's status page is written by people. Our probes add a regional reading beside it.

Our check readingRegional reading
  • 0Checks failing
  • 23Awaiting data
  • 602Checks passing

Live counts of check readings for the 626 services whose status feed we cannot read, taken from 10 regions. For the other 320, the vendor's own statement leads on the board below. How this check works

Two records, side by side

The vendor's own feed, and our check readings from each region beside it.

What comes with it

Everything the tracker ships with.

946 services

The tools developers depend on, with a check reading taken on a schedule.

10 regions, separately

Each region's check reading is shown separately.

Our own readings

We make one unauthenticated request from each region and show the vendor's own status beside it. How this check works

Share links

Every service has a share link for the moment the team chat asks: is it just me?

How it works

From question to answer in three steps.

01

Open the tracker

No account, no card. The board shows each tracked service's latest check reading.

02

Check the service

Each service page shows the regional readings and recent history, probed by us.

03

Share the answer

Send the share link to the team chat to compare what your network and our checks show. Many services down at once? See whether they share a provider.

RealUptime is not affiliated with any service it tracks. Names identify what we measured; nothing on this board speaks for a vendor's own team. Read the methodology. The incidents vendors declared on their own status pages are summarised month by month.

Free to read. It is also our best demo. The same fleet checking these services can check your own.