Each card is one fleet region's view of the whole public catalog: the median (p50), p95 and p99 response time over the latest hour, the 7-day baseline, and the last 24 hours as a line. A region reads slower than usual only after three consecutive hours well over its baseline; the rule is stated below. Read as a feed: Atom; as data: JSON.
Right now, by region
Tracking since the first rollup
The observatory has no daily bucket yet; the first rollup writes one. We do not call a figure "typical for a region" from a record shorter than 30 days, and this one is 30 days short. Until then the cards compare the latest hour with the last 7 days, which is all the record supports.
US-East
No readings yetNo hourly bucket has cleared the sample floor for this region yet.
US-West
No readings yetNo hourly bucket has cleared the sample floor for this region yet.
Europe
No readings yetNo hourly bucket has cleared the sample floor for this region yet.
Asia-Pacific
No readings yetNo hourly bucket has cleared the sample floor for this region yet.
US-Central
No readings yetNo hourly bucket has cleared the sample floor for this region yet.
Canada
No readings yetNo hourly bucket has cleared the sample floor for this region yet.
UK
No readings yetNo hourly bucket has cleared the sample floor for this region yet.
Southeast Asia
No readings yetNo hourly bucket has cleared the sample floor for this region yet.
Australia
No readings yetNo hourly bucket has cleared the sample floor for this region yet.
South America
No readings yetNo hourly bucket has cleared the sample floor for this region yet.
No hourly bucket has been written yet; the first rollup writes one.
Last 30 days, daily
No daily buckets yet. The first full day appears after the rollup has run over it.
What this is, and is not
Every figure on this page is a percentile of response times our own probes measured from 10 named fleet regions (US-East, US-West, Europe, Asia-Pacific, US-Central, Canada, UK, Southeast Asia, Australia, South America) against the public, unauthenticated endpoints of the ~195 services in our public outage catalog. It is a picture of how the internet looked from each vantage point, not a reading of any one service.
Not customer traffic. Customer monitoring data never enters this aggregate: the job reads one table, the catalog's own raw probe results, and nothing else. There is nothing to anonymize because nothing private goes in.
Only successful readings (HTTP 2xx with a recorded latency) count; failed and filtered readings carry no response time worth aggregating. Hourly and daily buckets under the sample floor are left out rather than drawn. A region reads slower than usual only after 3 consecutive hours with a median above 1.5x its 7-day baseline, and clears on the first hour at or under 1.25x, so a region hovering around the line does not flap. The 7-day baseline is the median of the region's hourly medians over the 7 days before the hour being judged.
Hourly buckets are kept for 90 days and daily buckets indefinitely. The words “typical for a region” are not used on this page until the record is 30 days old; the same claim guard that gates our research section decides. Methodology in force: version v2-2026-08-22.
Embed or cite
The daily chart and a per-region badge are plain SVG, cacheable and hotlinkable from anywhere, with “Source: RealUptime” and this page's address drawn into the picture. Link back to https://realuptime.io/outages/internet-weather when you quote a figure.
<a href="https://realuptime.io/outages/internet-weather"><img src="https://realuptime.io/outages/internet-weather/chart.svg?kind=daily" alt="Internet weather by region, RealUptime" width="720" height="290"></a>
<a href="https://realuptime.io/outages/internet-weather"><img src="https://realuptime.io/outages/internet-weather/chart.svg?kind=badge®ion=iad" alt="US-East internet weather, RealUptime" height="34"></a>