Skip to content

Outage tracker / Facebook

Is Facebook down?

I'm having a problem

Partially degradedchecked moments ago

Facebook is answering our probes, but its Sign-in is running at least 6.2x its 7-day median from US-Central. Everything else we check answered at its usual speed.

As of Nov 5, 2026, 3:43 PM UTC, RealUptime's checks of Facebook passed in all 10 regions that returned a reading.

Front-door and live API checks

Our checks of Facebook did not fail from two or more distant regions in the 77 days we have checked it (since Aug 20, 2026). This does not show Facebook works for users.

Email me when our checks of Facebook fail from two or more distant regions

One email when our checks of Facebook fail from two or more distant regions, and one when they pass, after you confirm the address. No account, no card.

This is our own reading from outside. It is not Facebook's official status.

our check readinglive · checked Nov 5, 2026, 3:43 PM UTC
US-East1538 msChecks passing
US-West607 msChecks passing
Europe420 msChecks passing
Asia-Pacific773 msChecks passing
US-Central2208 msPartially degraded
Canada605 msChecks passing
UK222 msChecks passing
Southeast Asia830 msChecks passing
Australia1955 msChecks passing
South America1419 msChecks passing
their status pagetheir claim, not our reading

Facebook publishes no status feed we can read, so the only reading here is our check reading on the left.

Facebook response time, by region

US-East
1.6sp95 · 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-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 651ms2026-10-13 UTC: p95 614ms2026-10-14 UTC: p95 504ms2026-10-15 UTC: p95 505ms2026-10-16 UTC: p95 630ms2026-10-17 UTC: p95 777ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 812ms2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 1.1s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 1.0s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 559ms2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 1.6s
Oct 7Oct 21Nov 5
US-West
1.0sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 556ms2026-10-08 UTC: p95 600ms2026-10-09 UTC: p95 750ms2026-10-10 UTC: p95 624ms2026-10-11 UTC: p95 597ms2026-10-12 UTC: p95 617ms2026-10-13 UTC: p95 491ms2026-10-14 UTC: p95 626ms2026-10-15 UTC: p95 621ms2026-10-16 UTC: p95 548ms2026-10-17 UTC: p95 2.2s2026-10-18 UTC: p95 2.8s2026-10-19 UTC: p95 2.9s2026-10-20 UTC: p95 2.9s2026-10-21 UTC: p95 2.5s2026-10-22 UTC: p95 2.2s2026-10-23 UTC: p95 1.8s2026-10-24 UTC: p95 1.9s2026-10-25 UTC: p95 2.1s2026-10-26 UTC: p95 2.1s2026-10-27 UTC: p95 1.8s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 2.1s2026-10-30 UTC: p95 2.2s2026-10-31 UTC: p95 2.1s2026-11-01 UTC: p95 1.7s2026-11-02 UTC: p95 2.2s2026-11-03 UTC: p95 1.0s2026-11-04 UTC: p95 764ms2026-11-05 UTC: p95 1.0s
Oct 7Oct 21Nov 5
Europe
1.0sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 752ms2026-10-08 UTC: p95 532ms2026-10-09 UTC: p95 566ms2026-10-10 UTC: p95 528ms2026-10-11 UTC: p95 540ms2026-10-12 UTC: p95 510ms2026-10-13 UTC: p95 635ms2026-10-14 UTC: p95 533ms2026-10-15 UTC: p95 556ms2026-10-16 UTC: p95 606ms2026-10-17 UTC: p95 684ms2026-10-18 UTC: p95 827ms2026-10-19 UTC: p95 999ms2026-10-20 UTC: p95 892ms2026-10-21 UTC: p95 806ms2026-10-22 UTC: p95 849ms2026-10-23 UTC: p95 807ms2026-10-24 UTC: p95 678ms2026-10-25 UTC: p95 872ms2026-10-26 UTC: p95 868ms2026-10-27 UTC: p95 864ms2026-10-28 UTC: p95 662ms2026-10-29 UTC: p95 821ms2026-10-30 UTC: p95 728ms2026-10-31 UTC: p95 814ms2026-11-01 UTC: p95 772ms2026-11-02 UTC: p95 813ms2026-11-03 UTC: p95 969ms2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 1.0s
Oct 7Oct 21Nov 5
Asia-Pacific
1.2sp95 · 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-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 2.0s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.4s2026-10-20 UTC: p95 2.4s2026-10-21 UTC: p95 2.3s2026-10-22 UTC: p95 2.3s2026-10-23 UTC: p95 2.1s2026-10-24 UTC: p95 2.5s2026-10-25 UTC: p95 2.0s2026-10-26 UTC: p95 2.4s2026-10-27 UTC: p95 2.4s2026-10-28 UTC: p95 2.3s2026-10-29 UTC: p95 2.4s2026-10-30 UTC: p95 2.2s2026-10-31 UTC: p95 2.2s2026-11-01 UTC: p95 2.4s2026-11-02 UTC: p95 2.6s2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
US-Central
3.8sp95 · latest
5s2.5s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 482ms2026-10-08 UTC: p95 726ms2026-10-09 UTC: p95 841ms2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 485ms2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 834ms2026-10-14 UTC: p95 964ms2026-10-15 UTC: p95 782ms2026-10-16 UTC: p95 638ms2026-10-17 UTC: p95 3.0s2026-10-18 UTC: p95 3.4s2026-10-19 UTC: p95 3.5s2026-10-20 UTC: p95 2.5s2026-10-21 UTC: p95 2.8s2026-10-22 UTC: p95 3.1s2026-10-23 UTC: p95 2.8s2026-10-24 UTC: p95 2.4s2026-10-25 UTC: p95 2.5s2026-10-26 UTC: p95 2.5s2026-10-27 UTC: p95 2.4s2026-10-28 UTC: p95 2.6s2026-10-29 UTC: p95 2.5s2026-10-30 UTC: p95 3.2s2026-10-31 UTC: p95 2.2s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 2.3s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 3.8s
Oct 7Oct 21Nov 5
Canada
981msp95 · 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-10-07 UTC: p95 505ms2026-10-08 UTC: p95 778ms2026-10-09 UTC: p95 601ms2026-10-10 UTC: p95 515ms2026-10-11 UTC: p95 498ms2026-10-12 UTC: p95 530ms2026-10-13 UTC: p95 660ms2026-10-14 UTC: p95 763ms2026-10-15 UTC: p95 800ms2026-10-16 UTC: p95 906ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.4s2026-10-24 UTC: p95 1.3s2026-10-25 UTC: p95 3.5s2026-10-26 UTC: p95 3.6s2026-10-27 UTC: p95 2.9s2026-10-28 UTC: p95 3.0s2026-10-29 UTC: p95 2.8s2026-10-30 UTC: p95 2.8s2026-10-31 UTC: p95 2.8s2026-11-01 UTC: p95 2.5s2026-11-02 UTC: p95 958ms2026-11-03 UTC: p95 916ms2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 981ms
Oct 7Oct 21Nov 5
UK
488msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 517ms2026-10-08 UTC: p95 402ms2026-10-09 UTC: p95 444ms2026-10-10 UTC: p95 426ms2026-10-11 UTC: p95 557ms2026-10-12 UTC: p95 524ms2026-10-13 UTC: p95 437ms2026-10-14 UTC: p95 610ms2026-10-15 UTC: p95 797ms2026-10-16 UTC: p95 535ms2026-10-17 UTC: p95 646ms2026-10-18 UTC: p95 609ms2026-10-19 UTC: p95 584ms2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 1.6s2026-10-25 UTC: p95 1.0s2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 797ms2026-10-28 UTC: p95 1.0s2026-10-29 UTC: p95 749ms2026-10-30 UTC: p95 530ms2026-10-31 UTC: p95 608ms2026-11-01 UTC: p95 1.0s2026-11-02 UTC: p95 455ms2026-11-03 UTC: p95 1.0s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 488ms
Oct 7Oct 21Nov 5
Southeast Asia
2.1sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 2.1s2026-10-15 UTC: p95 2.8s2026-10-16 UTC: p95 1.8s2026-10-17 UTC: p95 2.2s2026-10-18 UTC: p95 3.3s2026-10-19 UTC: p95 1.9s2026-10-20 UTC: p95 3.1s2026-10-21 UTC: p95 2.7s2026-10-22 UTC: p95 2.1s2026-10-23 UTC: p95 2.0s2026-10-24 UTC: p95 2.9s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.9s2026-10-27 UTC: p95 2.5s2026-10-28 UTC: p95 3.1s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 2.2s2026-10-31 UTC: p95 2.5s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 2.3s2026-11-03 UTC: p95 2.7s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5
Australia
2.1sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.7s2026-10-11 UTC: p95 2.0s2026-10-12 UTC: p95 1.6s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 2.1s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 3.1s2026-10-21 UTC: p95 3.4s2026-10-22 UTC: p95 3.0s2026-10-23 UTC: p95 2.9s2026-10-24 UTC: p95 2.0s2026-10-25 UTC: p95 2.6s2026-10-26 UTC: p95 1.8s2026-10-27 UTC: p95 2.2s2026-10-28 UTC: p95 2.7s2026-10-29 UTC: p95 1.7s2026-10-30 UTC: p95 2.8s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 2.0s2026-11-02 UTC: p95 2.5s2026-11-03 UTC: p95 2.1s2026-11-04 UTC: p95 2.3s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5
South America
1.9sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 927ms2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.7s2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.5s2026-10-15 UTC: p95 686ms2026-10-16 UTC: p95 757ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 2.5s2026-10-21 UTC: p95 3.4s2026-10-22 UTC: p95 3.7s2026-10-23 UTC: p95 9.3s2026-10-24 UTC: p95 1.4s2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.4s2026-10-27 UTC: p95 2.7s2026-10-28 UTC: p95 3.0s2026-10-29 UTC: p95 2.6s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 2.0s2026-11-02 UTC: p95 2.3s2026-11-03 UTC: p95 5.0s2026-11-04 UTC: p95 4.3s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5

Check your own site while you wait on Facebook

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 Facebook. It cannot diagnose Facebook's own systems.

What we measured, function by function

Facebook 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 web 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.

  • WebprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • AuthUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • DevelopersUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • MarketplaceUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • MessengerUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • PagesUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • SDKUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Sign-inUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Degraded Answering, but 6.2x slower than its 7-day median.Canada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
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 our checks show, and what people reported

  • North America
    Partially degradedUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1538msstatus code: 200checked: Nov 5, 2026, 3:43 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Facebook normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 607msstatus code: 200checked: Nov 5, 2026, 3:41 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Facebook normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Partially degradedlatency: 2208msstatus code: 200checked: Nov 5, 2026, 3:42 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Facebook normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 605msstatus code: 200checked: Nov 5, 2026, 3:40 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Facebook normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1419msstatus code: 200checked: Nov 5, 2026, 3:43 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Facebook normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 420msstatus code: 200checked: Nov 5, 2026, 3:41 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Facebook normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 222msstatus code: 200checked: Nov 5, 2026, 3:42 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Facebook normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 773msstatus code: 200checked: Nov 5, 2026, 3:40 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Facebook normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 830msstatus code: 200checked: Nov 5, 2026, 3:40 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Facebook normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 1955msstatus code: 200checked: Nov 5, 2026, 3:42 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Facebook 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 Facebook, 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 started counting reports for Facebook on September 16, 2026.

Recent probe events

No probe events on record yet for Facebook.

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

We have been measuring Facebook 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 Facebook covering any window you pick, with our check readings and Facebook's own claim at the time, side by side.

Full check history for Facebook: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Put this badge in your README

Facebook uptime by RealUptime's checksLive, from this page's own readings.
[![Facebook uptime by RealUptime's checks](https://realuptime.io/outages/facebook/badge.svg?days=30)](https://realuptime.io/outages/facebook)
<a href="https://realuptime.io/outages/facebook"><img src="https://realuptime.io/outages/facebook/badge.svg?days=30" alt="Facebook uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Facebook down?", https://realuptime.io/outages/facebook. The readings change with every check, so give the date you read them.

How our checks compare with Facebook's stated SLA

At or above your target

Our checks of Facebook failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, not from Facebook'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

secondaryfunctional: auth surface
https://graph.facebook.com/v19.0/me
primary
https://www.facebook.com/
secondary
https://www.facebook.com/facebook
secondary
https://www.messenger.com/
secondary
https://www.facebook.com/login/
secondary
https://www.facebook.com/marketplace/
secondary
https://connect.facebook.net/en_US/sdk.js
secondary
https://developers.facebook.com/
RealUptime is not affiliated with Facebook; the name identifies what we checked, and nothing here speaks for Facebook's own team. We send a single web request to Facebook from 10 regions on our own schedule and time the response. We do not see inside Facebook's systems, do not use an account or real transaction, and are not the same signal Facebook's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Facebook is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.