Skip to content

Outage tracker / KeyCDN

Is KeyCDN down?

I'm having a problem

Operationalchecked 9 minutes ago

We reached KeyCDN from all 10 regions we check.

As of Oct 5, 2026, 8:07 PM UTC, KeyCDN answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 44 days we have measured KeyCDN (since Aug 22, 2026).

our independent probeslive · checked Oct 5, 2026, 8:07 PM UTC
US-East694 msOperational
US-West1002 msOperational
Europe283 msOperational
Asia-Pacific1164 msOperational
US-Central660 msOperational
Canada472 msOperational
UK301 msOperational
Southeast Asia713 msOperational
Australia1272 msOperational
South America1078 msOperational
their status pagetheir claim, not our reading

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

KeyCDN response time, by region

US-East
907msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 920ms2026-09-07 UTC: p95 858ms2026-09-08 UTC: p95 835ms2026-09-09 UTC: p95 898ms2026-09-10 UTC: p95 954ms2026-09-11 UTC: p95 940ms2026-09-12 UTC: p95 860ms2026-09-13 UTC: p95 931ms2026-09-14 UTC: p95 955ms2026-09-15 UTC: p95 911ms2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 984ms2026-09-19 UTC: p95 857ms2026-09-20 UTC: p95 952ms2026-09-21 UTC: p95 817ms2026-09-22 UTC: p95 784ms2026-09-23 UTC: p95 867ms2026-09-24 UTC: p95 906ms2026-09-25 UTC: p95 861ms2026-09-26 UTC: p95 835ms2026-09-27 UTC: p95 744ms2026-09-28 UTC: p95 829ms2026-09-29 UTC: p95 885ms2026-09-30 UTC: p95 965ms2026-10-01 UTC: p95 893ms2026-10-02 UTC: p95 749ms2026-10-03 UTC: p95 778ms2026-10-04 UTC: p95 894ms2026-10-05 UTC: p95 907ms
Sep 6Sep 20Oct 5
US-West
875msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 890ms2026-09-07 UTC: p95 896ms2026-09-08 UTC: p95 846ms2026-09-09 UTC: p95 776ms2026-09-10 UTC: p95 974ms2026-09-11 UTC: p95 704ms2026-09-12 UTC: p95 638ms2026-09-13 UTC: p95 627ms2026-09-14 UTC: p95 654ms2026-09-15 UTC: p95 863ms2026-09-16 UTC: p95 934ms2026-09-17 UTC: p95 858ms2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 949ms2026-09-20 UTC: p95 980ms2026-09-21 UTC: p95 922ms2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 1.0s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 930ms2026-09-27 UTC: p95 850ms2026-09-28 UTC: p95 862ms2026-09-29 UTC: p95 919ms2026-09-30 UTC: p95 915ms2026-10-01 UTC: p95 955ms2026-10-02 UTC: p95 946ms2026-10-03 UTC: p95 1.0s2026-10-04 UTC: p95 870ms2026-10-05 UTC: p95 875ms
Sep 6Sep 20Oct 5
Europe
213msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 306ms2026-09-07 UTC: p95 213ms2026-09-08 UTC: p95 239ms2026-09-09 UTC: p95 230ms2026-09-10 UTC: p95 532ms2026-09-11 UTC: p95 207ms2026-09-12 UTC: p95 233ms2026-09-13 UTC: p95 271ms2026-09-14 UTC: p95 249ms2026-09-15 UTC: p95 255ms2026-09-16 UTC: p95 281ms2026-09-17 UTC: p95 320ms2026-09-18 UTC: p95 308ms2026-09-19 UTC: p95 327ms2026-09-20 UTC: p95 346ms2026-09-21 UTC: p95 385ms2026-09-22 UTC: p95 361ms2026-09-23 UTC: p95 314ms2026-09-24 UTC: p95 385ms2026-09-25 UTC: p95 378ms2026-09-26 UTC: p95 397ms2026-09-27 UTC: p95 328ms2026-09-28 UTC: p95 346ms2026-09-29 UTC: p95 354ms2026-09-30 UTC: p95 305ms2026-10-01 UTC: p95 249ms2026-10-02 UTC: p95 235ms2026-10-03 UTC: p95 251ms2026-10-04 UTC: p95 229ms2026-10-05 UTC: p95 213ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.5sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.5s2026-09-07 UTC: p95 1.6s2026-09-08 UTC: p95 1.5s2026-09-09 UTC: p95 1.5s2026-09-10 UTC: p95 1.4s2026-09-11 UTC: p95 1.2s2026-09-12 UTC: p95 1.4s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 1.4s2026-09-17 UTC: p95 1.4s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.4s2026-09-20 UTC: p95 1.4s2026-09-21 UTC: p95 2.9s2026-09-22 UTC: p95 3.7s2026-09-23 UTC: p95 1.5s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 1.6s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.5s
Sep 6Sep 20Oct 5
US-Central
833msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 938ms2026-09-07 UTC: p95 836ms2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 882ms2026-09-11 UTC: p95 932ms2026-09-12 UTC: p95 939ms2026-09-13 UTC: p95 966ms2026-09-14 UTC: p95 860ms2026-09-15 UTC: p95 950ms2026-09-16 UTC: p95 899ms2026-09-17 UTC: p95 842ms2026-09-18 UTC: p95 892ms2026-09-19 UTC: p95 983ms2026-09-20 UTC: p95 835ms2026-09-21 UTC: p95 1.0s2026-09-22 UTC: p95 896ms2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 809ms2026-09-26 UTC: p95 900ms2026-09-27 UTC: p95 818ms2026-09-28 UTC: p95 940ms2026-09-29 UTC: p95 796ms2026-09-30 UTC: p95 881ms2026-10-01 UTC: p95 834ms2026-10-02 UTC: p95 817ms2026-10-03 UTC: p95 882ms2026-10-04 UTC: p95 1.0s2026-10-05 UTC: p95 833ms
Sep 6Sep 20Oct 5
Canada
783msp95 · latest
5s2.5s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 946ms2026-09-07 UTC: p95 908ms2026-09-08 UTC: p95 2.7s2026-09-09 UTC: p95 912ms2026-09-10 UTC: p95 973ms2026-09-11 UTC: p95 843ms2026-09-12 UTC: p95 717ms2026-09-13 UTC: p95 914ms2026-09-14 UTC: p95 845ms2026-09-15 UTC: p95 956ms2026-09-16 UTC: p95 906ms2026-09-17 UTC: p95 812ms2026-09-18 UTC: p95 939ms2026-09-19 UTC: p95 872ms2026-09-20 UTC: p95 750ms2026-09-21 UTC: p95 754ms2026-09-22 UTC: p95 846ms2026-09-23 UTC: p95 806ms2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 944ms2026-09-26 UTC: p95 989ms2026-09-27 UTC: p95 885ms2026-09-28 UTC: p95 862ms2026-09-29 UTC: p95 882ms2026-09-30 UTC: p95 900ms2026-10-01 UTC: p95 862ms2026-10-02 UTC: p95 850ms2026-10-03 UTC: p95 852ms2026-10-04 UTC: p95 957ms2026-10-05 UTC: p95 783ms
Sep 6Sep 20Oct 5
UK
345msp95 · latest
5s2.5s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 333ms2026-09-07 UTC: p95 272ms2026-09-08 UTC: p95 2.8s2026-09-09 UTC: p95 565ms2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 260ms2026-09-12 UTC: p95 260ms2026-09-13 UTC: p95 267ms2026-09-14 UTC: p95 210ms2026-09-15 UTC: p95 243ms2026-09-16 UTC: p95 222ms2026-09-17 UTC: p95 286ms2026-09-18 UTC: p95 315ms2026-09-19 UTC: p95 305ms2026-09-20 UTC: p95 308ms2026-09-21 UTC: p95 321ms2026-09-22 UTC: p95 440ms2026-09-23 UTC: p95 331ms2026-09-24 UTC: p95 353ms2026-09-25 UTC: p95 395ms2026-09-26 UTC: p95 351ms2026-09-27 UTC: p95 350ms2026-09-28 UTC: p95 468ms2026-09-29 UTC: p95 345ms2026-09-30 UTC: p95 356ms2026-10-01 UTC: p95 358ms2026-10-02 UTC: p95 332ms2026-10-03 UTC: p95 341ms2026-10-04 UTC: p95 368ms2026-10-05 UTC: p95 345ms
Sep 6Sep 20Oct 5
Southeast Asia
1.1sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 975ms2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 970ms2026-09-09 UTC: p95 1.4s2026-09-10 UTC: p95 1.2s2026-09-11 UTC: p95 1.0s2026-09-12 UTC: p95 1.0s2026-09-13 UTC: p95 1.0s2026-09-14 UTC: p95 978ms2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 1.0s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.0s2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 5
Australia
1.9sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.5s2026-09-07 UTC: p95 1.5s2026-09-08 UTC: p95 2.2s2026-09-09 UTC: p95 1.6s2026-09-10 UTC: p95 1.8s2026-09-11 UTC: p95 1.6s2026-09-12 UTC: p95 1.6s2026-09-13 UTC: p95 1.6s2026-09-14 UTC: p95 1.9s2026-09-15 UTC: p95 1.8s2026-09-16 UTC: p95 1.7s2026-09-17 UTC: p95 1.7s2026-09-18 UTC: p95 1.7s2026-09-19 UTC: p95 1.9s2026-09-20 UTC: p95 1.8s2026-09-21 UTC: p95 1.7s2026-09-22 UTC: p95 1.8s2026-09-23 UTC: p95 1.6s2026-09-24 UTC: p95 1.9s2026-09-25 UTC: p95 1.7s2026-09-26 UTC: p95 1.9s2026-09-27 UTC: p95 1.6s2026-09-28 UTC: p95 1.7s2026-09-29 UTC: p95 1.8s2026-09-30 UTC: p95 1.8s2026-10-01 UTC: p95 1.7s2026-10-02 UTC: p95 1.9s2026-10-03 UTC: p95 1.8s2026-10-04 UTC: p95 1.7s2026-10-05 UTC: p95 1.9s
Sep 6Sep 20Oct 5
South America
1.3sp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.6s2026-09-07 UTC: p95 1.4s2026-09-08 UTC: p95 1.6s2026-09-09 UTC: p95 1.3s2026-09-10 UTC: p95 1.6s2026-09-11 UTC: p95 1.4s2026-09-12 UTC: p95 1.4s2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.4s2026-09-15 UTC: p95 1.4s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 2.4s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.4s2026-09-20 UTC: p95 1.6s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.7s2026-09-23 UTC: p95 1.7s2026-09-24 UTC: p95 1.5s2026-09-25 UTC: p95 1.5s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 2.3s2026-09-30 UTC: p95 1.4s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.7s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.3s
Sep 6Sep 20Oct 5

Is it KeyCDN, 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 KeyCDN -- it cannot diagnose KeyCDN's own systems.

What we measured, function by function

KeyCDN 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: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see KeyCDN go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching KeyCDN, and again when they can reach it again. That is our own measurement from ten regions, not KeyCDN's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

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
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 694msstatus code: 401checked: Oct 5, 2026, 7:50 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach KeyCDN normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 1002msstatus code: 401checked: Oct 5, 2026, 8:07 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach KeyCDN normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 660msstatus code: 401checked: Oct 5, 2026, 7:17 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach KeyCDN normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 472msstatus code: 401checked: Oct 5, 2026, 7:26 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach KeyCDN normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 1078msstatus code: 401checked: Oct 5, 2026, 7:24 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach KeyCDN normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 283msstatus code: 401checked: Oct 5, 2026, 7:51 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach KeyCDN normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 301msstatus code: 401checked: Oct 5, 2026, 7:23 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach KeyCDN normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 1164msstatus code: 401checked: Oct 5, 2026, 8:06 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach KeyCDN normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 713msstatus code: 401checked: Oct 5, 2026, 7:38 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach KeyCDN normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 1272msstatus code: 401checked: Oct 5, 2026, 7:54 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach KeyCDN normally. We do not have enough reports from Australia to say anything about what people there are seeing.

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

These are unverified reports from people using KeyCDN, 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 KeyCDN yet, which is not evidence that nothing is wrong.

Recent outages

No outages on record yet for KeyCDN.

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

We have been measuring KeyCDN since August 22, 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 KeyCDN covering any window you pick, with our measurements and KeyCDN's own claim at the time, side by side.

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

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

KeyCDN uptime measured by RealUptimeLive, from this page's own readings.
[![KeyCDN uptime measured by RealUptime](https://realuptime.io/outages/keycdn/badge.svg?days=30)](https://realuptime.io/outages/keycdn)
<a href="https://realuptime.io/outages/keycdn"><img src="https://realuptime.io/outages/keycdn/badge.svg?days=30" alt="KeyCDN 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 KeyCDN's SLA implies, from our measurement

At or above your target

We measured none of downtime for KeyCDN 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 KeyCDN'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://api.keycdn.com/zones.json
secondary
https://www.keycdn.com/
secondary
https://status.keycdn.com/
RealUptime is not affiliated with KeyCDN; the name identifies what we measured, and nothing here speaks for KeyCDN's own team. We send a single web request to KeyCDN from 10 regions on our own schedule and time the response. We do not see inside KeyCDN's systems, do not use an account or real transaction, and are not the same signal KeyCDN's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for KeyCDN 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. Read the full methodology.