Skip to content

Outage tracker / Peacock

Is Peacock down?

I'm having a problem

Operationalchecked 20 minutes ago

We reached Peacock from all 2 regions we check.

As of Oct 5, 2026, 7:57 PM UTC, Peacock answered RealUptime's probes in all 2 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 46 days we have measured Peacock (since Aug 20, 2026).

Email me the next time we see Peacock go down

Measured by our own probes from ten regions, not Peacock's status page. One email when a measured outage opens and one when it closes, after you confirm the address. No account, no card.

our independent probeslive · checked Oct 5, 2026, 7:57 PM UTC
US-East176 msOperational
US-West604 msOperational

Peacock streams to United States viewers, so we check it from our US regions only.

their status pagetheir claim, not our reading

Peacock publishes no status feed we can read, so the only independent reading here is ours on the left.

Peacock response time, by region

US-East
459msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 256ms2026-09-07 UTC: p95 374ms2026-09-08 UTC: p95 329ms2026-09-09 UTC: p95 323ms2026-09-10 UTC: p95 383ms2026-09-11 UTC: p95 396ms2026-09-12 UTC: p95 346ms2026-09-13 UTC: p95 398ms2026-09-14 UTC: p95 319ms2026-09-15 UTC: p95 495ms2026-09-16 UTC: p95 528ms2026-09-17 UTC: p95 498ms2026-09-18 UTC: p95 484ms2026-09-19 UTC: p95 469ms2026-09-20 UTC: p95 705ms2026-09-21 UTC: p95 487ms2026-09-22 UTC: p95 457ms2026-09-23 UTC: p95 508ms2026-09-24 UTC: p95 710ms2026-09-25 UTC: p95 536ms2026-09-26 UTC: p95 424ms2026-09-27 UTC: p95 617ms2026-09-28 UTC: p95 496ms2026-09-29 UTC: p95 495ms2026-09-30 UTC: p95 476ms2026-10-01 UTC: p95 394ms2026-10-02 UTC: p95 546ms2026-10-03 UTC: p95 493ms2026-10-04 UTC: p95 446ms2026-10-05 UTC: p95 459ms
Sep 6Sep 20Oct 5
US-West
778msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 785ms2026-09-07 UTC: p95 578ms2026-09-08 UTC: p95 474ms2026-09-09 UTC: p95 480ms2026-09-10 UTC: p95 414ms2026-09-11 UTC: p95 522ms2026-09-12 UTC: p95 506ms2026-09-13 UTC: p95 397ms2026-09-14 UTC: p95 424ms2026-09-15 UTC: p95 623ms2026-09-16 UTC: p95 620ms2026-09-17 UTC: p95 631ms2026-09-18 UTC: p95 607ms2026-09-19 UTC: p95 609ms2026-09-20 UTC: p95 629ms2026-09-21 UTC: p95 556ms2026-09-22 UTC: p95 745ms2026-09-23 UTC: p95 661ms2026-09-24 UTC: p95 661ms2026-09-25 UTC: p95 731ms2026-09-26 UTC: p95 740ms2026-09-27 UTC: p95 667ms2026-09-28 UTC: p95 768ms2026-09-29 UTC: p95 645ms2026-09-30 UTC: p95 715ms2026-10-01 UTC: p95 702ms2026-10-02 UTC: p95 748ms2026-10-03 UTC: p95 798ms2026-10-04 UTC: p95 629ms2026-10-05 UTC: p95 778ms
Sep 6Sep 20Oct 5

Is it Peacock, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Peacock -- it cannot diagnose Peacock's own systems.

What we measured, function by function

Peacock answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: Not monitored from this regionAsia-Pacific: Not monitored from this regionUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: Not monitored from this regionAsia-Pacific: Not monitored from this regionUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    Not monitored from this regionUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 176msstatus code: 403checked: Oct 5, 2026, 7:57 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Peacock normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 604msstatus code: 403checked: Oct 5, 2026, 7:47 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Peacock normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Not monitored from this regionPeacock is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Canada
      Not monitored from this regionPeacock is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionPeacock is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Europe
    Not monitored from this regionEurope, UK
    • Europe
      Not monitored from this regionPeacock is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • UK
      Not monitored from this regionPeacock is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • Asia Pacific
    Not monitored from this regionAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Not monitored from this regionPeacock is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Southeast Asia
      Not monitored from this regionPeacock is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Australia
      Not monitored from this regionPeacock is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Peacock, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Peacock yet, which is not evidence that nothing is wrong.

Recent outages

No outages on record yet for Peacock.

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Peacock since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Peacock covering any window you pick, with our measurements and Peacock's own claim at the time, side by side.

Full availability history for Peacock: 90-day availability by region, month-by-month uptime, and every incident on record.

Put this badge in your README

Peacock uptime measured by RealUptimeLive, from this page's own readings.
[![Peacock uptime measured by RealUptime](https://realuptime.io/outages/peacock/badge.svg?days=30)](https://realuptime.io/outages/peacock)
<a href="https://realuptime.io/outages/peacock"><img src="https://realuptime.io/outages/peacock/badge.svg?days=30" alt="Peacock uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Peacock's SLA implies, from our measurement

At or above your target

We measured none of downtime for Peacock over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Peacock's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://ovp.peacocktv.com/auth/users/me
secondary
https://www.peacocktv.com/
RealUptime is not affiliated with Peacock; the name identifies what we measured, and nothing here speaks for Peacock's own team. We send a single web request to Peacock from 2 regions on our own schedule and time the response. We do not see inside Peacock's systems, do not use an account or real transaction, and are not the same signal Peacock's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Peacock is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Peacock streams to United States viewers, so we check it from our US regions only. Read the full methodology.