Skip to main content
Vendor reliability

Vendor record

Fastly

Vendor reports Degraded

Checked

Front door check counts and Fastly’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.

Front door checks

We send a request to a documented Fastly endpoint and count the checks that got the answer it is documented to give.

  • Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    Endpoint checked
    api.fastly.com
    Scope
    apiNo vendor region
    First check in this window
    Latest clear answer

Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Fastly product, region or your app worked.

How we count front door checks

Fastly says

Incident posts from Fastly’s status page, with its titles, impact levels and times. They say what Fastly chose to post, not what reached your app.

A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.

3

incidents Fastly posted, last 30 days

All vendors’ incidents

Most recent records · all dates

  • Elevated Errors for Singapore (QPG)

    Major

    Started, per Fastly

    Latest status Fastly postedInvestigating. No resolution posted.

    Fastly’s post

  • Elevated Errors for API & Configuration Management

    Major

    Started, per Fastly

    Closed in our record(7d 3h)

    Fastly’s post

  • Elevated Errors for Object Storage

    Major

    Started, per Fastly

    Closed in our record(5d 1h)

    Fastly’s post

  • Elevated Errors for Support Ticketing System

    Major

    Started, per Fastly

    Closed in our record(9h 23m)

    Fastly’s post

  • Elevated Errors for Compute

    Major

    Started, per Fastly

    Closed in our record(3h 37m)

    Fastly’s post
15 older records

  • Elevated Errors for Compute

    Major

    Started, per Fastly

    Closed in our record(4d 3h)

    Fastly’s post

  • Update to waitlist disconnect response codes

    Major

    Started, per Fastly

    Closed in our record(12d 23h)

    Fastly’s post

  • Update: Confirmed third-party network event impacting our Los Angeles region

    Major

    Started, per Fastly

    Closed in our record(1d 6h)

    Fastly’s post

  • Elevated Errors for Manila (MNL)

    Major

    Started, per Fastly

    Closed in our record(10h 3m)

    Fastly’s post

  • Performance Issues with Dashboard Data

    Major

    Started, per Fastly

    Closed in our record(2d 8h)

    Fastly’s post

  • Elevated Errors for Chicago (CHI)

    Major

    Started, per Fastly

    Closed in our record(3h 22m)

    Fastly’s post

  • Reduced cache performance for Compute services

    Major

    Started, per Fastly

    Closed in our record(16h 48m)

    Fastly’s post

  • CDN Global Performance Impact

    Major

    Started, per Fastly

    Closed in our record(6h 28m)

    Fastly’s post

  • Impacted performance to our Content Delivery (CDN)

    Major

    Started, per Fastly

    Closed in our record(7d 11h)

    Fastly’s post

  • Elevated Errors for API & Configuration Management

    Major

    Started, per Fastly

    Closed in our record(3h 34m)

    Fastly’s post

  • Possible Errors for API & Configuration Management

    Major

    Started, per Fastly

    Closed in our record(1h 57m)

    Fastly’s post

  • Image Optimizer Performance Issues

    Major

    Started, per Fastly

    Closed in our record(16h 42m)

    Fastly’s post

  • Elevated Latency for Singapore (SIN)

    Major

    Started, per Fastly

    Closed in our record(6h 33m)

    Fastly’s post

  • Elevated Errors for Palo Alto (PAO)

    Major

    Started, per Fastly

    Closed in our record(1h 4m)

    Fastly’s post

  • Buenos Aires (EZE) with Possible Impact

    Major

    Started, per Fastly

    Closed in our record(22m)

    Fastly’s post

Your code, your dependencies

See which of your code paths call Fastly

Connect GitHub or GitLab to find where your public or private repository uses Fastly. Review each match and your alert settings.

Connect a repository

Free to start. No credit card.

Use this record on your site

Add Fastly status to your page.

Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.

Appearance
Detail
Preview · FastlyStatus only

For HTML pages that permit CheckUpstream frames. Loads a snapshot; reload the containing page for a newer reading. Theme and detail settings apply to this format.

Iframe snippet
<iframe src="https://checkupstream.com/embed/fastly?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="Fastly status badge"></iframe>

Frequently Asked Questions

Is Fastly currently down?

Fastly's latest recorded status is Degraded. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.

When did Fastly last have an outage?

The most recent closed incident record began 10 days ago and spans 7d 3h. The vendor reported a partial outage. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.

Does CheckUpstream publish an uptime percentage for Fastly?

No. CheckUpstream checks Fastly’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.

How do I monitor Fastly in production?

Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.

How does CheckUpstream track Fastly?

This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.

Related vendors