The State of Uptime 2026

• 4.7 h

  average time from first failure to recovery

• 9.9%

  of outages lasted longer than an hour

• 25%

  of outages began on a Saturday or Sunday

• How long outages last

  Confirmed outages by duration

  Under 5 min46%

  5–30 min37%

  30 min–1 h7.3%

  1–6 h7.6%

  Over 6 h2.3%

• When outages start

  Confirmed outage starts by hour of day (UTC). Busiest hour in red.

  00:0006:0012:0018:00

  The busiest hour is 15:00 UTC. 23% of outages start between 00:00 and 06:00 UTC.

Based on 2,201,561 confirmed outages. Timestamps are aggregated in UTC; a view in each monitor’s local time is planned once monitors carry a time zone.

• Page views rated Good

  Share of real page views meeting Google’s Good threshold, desktop and mobile

  LCP loading

  Desktop66%

  Mobile65%

  INP responsiveness

  Desktop82%

  Mobile70%

  CLS visual stability

  Desktop81%

  Mobile83%

• 75th percentile, by device

  Three in four page views were at least this good

  Vital	Desktop	Mobile	Mobile vs desktop
  LCP	2.46 s	2.45 s	0%
  INP	106 ms	200 ms	+89%
  CLS	0.06	0.09	+49%

  LCP is Largest Contentful Paint, INP is Interaction to Next Paint and CLS is Cumulative Layout Shift. Lower is better for all three.

• 274.1

  errors per 1,000 page views, JavaScript and failed requests together

• 59%

  of errors were failed network requests; 41% were JavaScript exceptions

• 1.5×

  as many errors per page view on mobile as on desktop

• Failed requests by status

  Share of failed network requests by HTTP status

  No response (blocked, cancelled or offline)89%

  400 Bad Request3.6%

  422 Unprocessable Content3%

  404 Not Found1.1%

  403 Forbidden1%

  502 Bad Gateway1%

  500 Internal Server Error0.3%

  429 Too Many Requests0.3%

  504 Gateway Timeout0.1%

  401 Unauthorized0.1%

  “No response” means the browser never got an HTTP status back: the request was blocked by an extension or CORS, cancelled by navigation, or the visitor was offline. Linked codes open a guide to the error.

• Errors by browser

  Share of all client-side errors

  Chrome62%

  Safari21%

  Firefox6.7%

  Edge5.9%

  Samsung Internet1.2%

  Opera0.7%

  Yandex Browser0.1%

  Other3%

  Largely a mirror of browser market share. Bots, in-app browsers and unrecognized user agents are counted under Other.

Based on 2,249,100 real-user page views.

• 2.4%

  of domains expire within the next 30 days

• 8.2 yrs

  average age of a monitored domain

• 46%

  end in .com, still the default

• 68%

  have a registrar transfer lock

• Most common endings

  Share of monitored domains by top-level domain

  .com46%

  .org4.2%

  .de3.5%

  .net3.2%

  .com.au2.1%

  .co.uk2%

  .io1.8%

  .dev1.8%

  .cz1.6%

  .ch1.3%

• Registrars

  Share of monitored domains by registrar

  Registrar	Share
  GoDaddy.com	16%
  NameCheap	9.3%
  Cloudflare	9.2%
  Spaceship	4%
  Tucows Domains	2.8%
  Global Domains International	2.7%
  Porkbun	2.5%
  Amazon Registrar	2.3%
  Netregistry Wholesale	1.9%
  HOSTINGER operations	1.9%

Registry data came from RDAP for 86% of domains and from WHOIS for 11%. Based on 2,214 monitored domains.

• 63,578

  incidents reported by tracked services

• 2.1 h

  median time for a service to resolve an incident

• 35%

  were rated major or critical by the provider

• 1.4%

  were planned maintenance rather than outages

• Incidents by category

  The eight categories that reported the most incidents

  Payment Processing5,251

  Financial Services3,207

  Security Operations3,028

  Education Technology2,544

  AI & ML Platforms2,539

  E-Commerce2,362

  VoIP & Communication2,341

  Cloud Platforms2,114

  The other 144 categories reported 40,192 incidents between them.

• Which status page platform they use

  Share of tracked services by status page platform

  Atlassian Statuspage87%

  Instatus5.4%

  Better Stack5.2%

  incident.io1.6%

  OpenStatus0.2%

  Their own or another platform0.2%

Impact and timing are each provider’s own classification, taken from its status page. Separately, 35% of the outage reports visitors submit on Pulsetic’s public status pages came from Europe.

• 1. Real checks, not a survey

     Every figure comes from production monitoring: HTTP, TCP, ping, heartbeat, SSL and domain checks, pooled across the whole network.

  2. Confirmed from another location

     A monitor only counts as down once a second location confirms the failure, so a blip seen from one location never lowers the uptime figure.

  3. Blips excluded

     An outage runs from the first failed check to the first successful one. Sub-minute flaps that recover on their own are filtered out.

  4. Timestamps in UTC

     Hour-of-day and day-of-week patterns are aggregated in UTC. Response time is the full request, averaged across HTTP checks.

  5. Aggregated and anonymized

     Nothing here identifies a customer, a domain or an individual website. Each section states its own sample size.

• What this edition covers

  • WindowSep 2025 to Sep 2026
  • Confirmed outages2,201,561
  • Real-user page views2,249,100
  • SSL certificates74,448
  • Domains2,214
  • Cron job monitors3,347
  • Third-party status incidents63,578

  Cite this report

  “The State of Uptime 2026”, Pulsetic, pulsetic.com/uptime-statistics/, figures as of 24 September 2026.