Skip to content

Outage tracker / Instagram

Is Instagram down?

I'm having a problem

Checks passingchecked moments ago

Our checks of Instagram pass from all 10 regions we check.

As of Oct 19, 2026, 9:29 PM UTC, RealUptime's checks of Instagram passed in all 10 regions that returned a reading.

Front-door and live API checks

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

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

One email when our checks of Instagram 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 Instagram's official status.

our check readinglive · checked Oct 19, 2026, 9:29 PM UTC
US-East767 msChecks passing
US-West586 msChecks passing
Europe871 msChecks passing
Asia-Pacific980 msChecks passing
US-Central683 msChecks passing
Canada786 msChecks passing
UK461 msChecks passing
Southeast Asia2157 msChecks passing
Australia1604 msChecks passing
South America1005 msChecks passing
their status pagetheir claim, not our reading

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

Instagram response time, by region

US-East
1.1sp95 · 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-20 UTC: p95 438ms2026-09-21 UTC: p95 393ms2026-09-22 UTC: p95 442ms2026-09-23 UTC: p95 427ms2026-09-24 UTC: p95 403ms2026-09-25 UTC: p95 374ms2026-09-26 UTC: p95 442ms2026-09-27 UTC: p95 469ms2026-09-28 UTC: p95 566ms2026-09-29 UTC: p95 512ms2026-09-30 UTC: p95 488ms2026-10-01 UTC: p95 725ms2026-10-02 UTC: p95 756ms2026-10-03 UTC: p95 790ms2026-10-04 UTC: p95 870ms2026-10-05 UTC: p95 1.4s2026-10-06 UTC: p95 1.5s2026-10-07 UTC: p95 1.6s2026-10-08 UTC: p95 1.5s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 552ms2026-10-13 UTC: p95 618ms2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 800ms2026-10-16 UTC: p95 607ms2026-10-17 UTC: p95 799ms2026-10-18 UTC: p95 832ms2026-10-19 UTC: p95 1.1s
Sep 20Oct 4Oct 19
US-West
1.2sp95 · 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-20 UTC: p95 710ms2026-09-21 UTC: p95 546ms2026-09-22 UTC: p95 497ms2026-09-23 UTC: p95 559ms2026-09-24 UTC: p95 832ms2026-09-25 UTC: p95 579ms2026-09-26 UTC: p95 636ms2026-09-27 UTC: p95 642ms2026-09-28 UTC: p95 598ms2026-09-29 UTC: p95 526ms2026-09-30 UTC: p95 533ms2026-10-01 UTC: p95 632ms2026-10-02 UTC: p95 601ms2026-10-03 UTC: p95 555ms2026-10-04 UTC: p95 572ms2026-10-05 UTC: p95 524ms2026-10-06 UTC: p95 518ms2026-10-07 UTC: p95 564ms2026-10-08 UTC: p95 482ms2026-10-09 UTC: p95 513ms2026-10-10 UTC: p95 567ms2026-10-11 UTC: p95 543ms2026-10-12 UTC: p95 558ms2026-10-13 UTC: p95 524ms2026-10-14 UTC: p95 787ms2026-10-15 UTC: p95 719ms2026-10-16 UTC: p95 615ms2026-10-17 UTC: p95 795ms2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.2s
Sep 20Oct 4Oct 19
Europe
1.1sp95 · 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-09-20 UTC: p95 386ms2026-09-21 UTC: p95 398ms2026-09-22 UTC: p95 374ms2026-09-23 UTC: p95 402ms2026-09-24 UTC: p95 425ms2026-09-25 UTC: p95 362ms2026-09-26 UTC: p95 404ms2026-09-27 UTC: p95 425ms2026-09-28 UTC: p95 405ms2026-09-29 UTC: p95 387ms2026-09-30 UTC: p95 390ms2026-10-01 UTC: p95 607ms2026-10-02 UTC: p95 548ms2026-10-03 UTC: p95 587ms2026-10-04 UTC: p95 542ms2026-10-05 UTC: p95 808ms2026-10-06 UTC: p95 1.0s2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 651ms2026-10-10 UTC: p95 685ms2026-10-11 UTC: p95 952ms2026-10-12 UTC: p95 875ms2026-10-13 UTC: p95 1.5s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 645ms2026-10-16 UTC: p95 966ms2026-10-17 UTC: p95 864ms2026-10-18 UTC: p95 637ms2026-10-19 UTC: p95 1.1s
Sep 20Oct 4Oct 19
Asia-Pacific
1.5sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 808ms2026-09-21 UTC: p95 820ms2026-09-22 UTC: p95 854ms2026-09-23 UTC: p95 763ms2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 794ms2026-09-26 UTC: p95 911ms2026-09-27 UTC: p95 904ms2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 903ms2026-09-30 UTC: p95 857ms2026-10-01 UTC: p95 838ms2026-10-02 UTC: p95 828ms2026-10-03 UTC: p95 848ms2026-10-04 UTC: p95 931ms2026-10-05 UTC: p95 846ms2026-10-06 UTC: p95 911ms2026-10-07 UTC: p95 936ms2026-10-08 UTC: p95 874ms2026-10-09 UTC: p95 920ms2026-10-10 UTC: p95 878ms2026-10-11 UTC: p95 962ms2026-10-12 UTC: p95 881ms2026-10-13 UTC: p95 986ms2026-10-14 UTC: p95 906ms2026-10-15 UTC: p95 1.0s2026-10-16 UTC: p95 1.0s2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.5s
Sep 20Oct 4Oct 19
US-Central
1.3sp95 · 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-20 UTC: p95 895ms2026-09-21 UTC: p95 866ms2026-09-22 UTC: p95 878ms2026-09-23 UTC: p95 875ms2026-09-24 UTC: p95 850ms2026-09-25 UTC: p95 913ms2026-09-26 UTC: p95 872ms2026-09-27 UTC: p95 927ms2026-09-28 UTC: p95 941ms2026-09-29 UTC: p95 922ms2026-09-30 UTC: p95 859ms2026-10-01 UTC: p95 1.0s2026-10-02 UTC: p95 998ms2026-10-03 UTC: p95 917ms2026-10-04 UTC: p95 927ms2026-10-05 UTC: p95 976ms2026-10-06 UTC: p95 976ms2026-10-07 UTC: p95 929ms2026-10-08 UTC: p95 944ms2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 959ms2026-10-11 UTC: p95 937ms2026-10-12 UTC: p95 967ms2026-10-13 UTC: p95 964ms2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 999ms2026-10-16 UTC: p95 788ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s
Sep 20Oct 4Oct 19
Canada
1.4sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 444ms2026-09-21 UTC: p95 671ms2026-09-22 UTC: p95 600ms2026-09-23 UTC: p95 600ms2026-09-24 UTC: p95 560ms2026-09-25 UTC: p95 461ms2026-09-26 UTC: p95 490ms2026-09-27 UTC: p95 485ms2026-09-28 UTC: p95 508ms2026-09-29 UTC: p95 504ms2026-09-30 UTC: p95 610ms2026-10-01 UTC: p95 579ms2026-10-02 UTC: p95 555ms2026-10-03 UTC: p95 563ms2026-10-04 UTC: p95 568ms2026-10-05 UTC: p95 619ms2026-10-06 UTC: p95 757ms2026-10-07 UTC: p95 671ms2026-10-08 UTC: p95 588ms2026-10-09 UTC: p95 630ms2026-10-10 UTC: p95 544ms2026-10-11 UTC: p95 510ms2026-10-12 UTC: p95 594ms2026-10-13 UTC: p95 869ms2026-10-14 UTC: p95 1.6s2026-10-15 UTC: p95 1.6s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.4s
Sep 20Oct 4Oct 19
UK
1.1sp95 · 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-09-20 UTC: p95 383ms2026-09-21 UTC: p95 487ms2026-09-22 UTC: p95 535ms2026-09-23 UTC: p95 394ms2026-09-24 UTC: p95 428ms2026-09-25 UTC: p95 503ms2026-09-26 UTC: p95 639ms2026-09-27 UTC: p95 568ms2026-09-28 UTC: p95 467ms2026-09-29 UTC: p95 507ms2026-09-30 UTC: p95 458ms2026-10-01 UTC: p95 681ms2026-10-02 UTC: p95 658ms2026-10-03 UTC: p95 691ms2026-10-04 UTC: p95 629ms2026-10-05 UTC: p95 1.0s2026-10-06 UTC: p95 691ms2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 701ms2026-10-10 UTC: p95 685ms2026-10-11 UTC: p95 699ms2026-10-12 UTC: p95 859ms2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 860ms2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.0s2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 893ms2026-10-19 UTC: p95 1.1s
Sep 20Oct 4Oct 19
Southeast Asia
2.1sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.5s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.2s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 2.0s2026-10-14 UTC: p95 2.0s2026-10-15 UTC: p95 1.8s2026-10-16 UTC: p95 1.7s2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.0s2026-10-19 UTC: p95 2.1s
Sep 20Oct 4Oct 19
Australia
2.3sp95 · 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-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.8s2026-09-22 UTC: p95 1.6s2026-09-23 UTC: p95 1.6s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.5s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.6s2026-10-03 UTC: p95 1.5s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.9s2026-10-06 UTC: p95 1.5s2026-10-07 UTC: p95 1.5s2026-10-08 UTC: p95 1.7s2026-10-09 UTC: p95 1.7s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 2.8s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.3s
Sep 20Oct 4Oct 19
South America
1.4sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 988ms2026-09-24 UTC: p95 876ms2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 948ms2026-09-28 UTC: p95 990ms2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.5s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.2s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.5s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.4s
Sep 20Oct 4Oct 19

Check your own site while you wait on Instagram

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

What we measured, function by function

Instagram 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
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
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 767msstatus code: 200checked: Oct 19, 2026, 9:29 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Instagram normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 586msstatus code: 200checked: Oct 19, 2026, 9:27 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Instagram normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 683msstatus code: 200checked: Oct 19, 2026, 9:28 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Instagram normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 786msstatus code: 200checked: Oct 19, 2026, 9:27 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Instagram normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1005msstatus code: 200checked: Oct 19, 2026, 9:28 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Instagram 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: 871msstatus code: 200checked: Oct 19, 2026, 9:29 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Instagram normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 461msstatus code: 200checked: Oct 19, 2026, 9:26 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Instagram 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: 980msstatus code: 200checked: Oct 19, 2026, 9:28 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Instagram normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 2157msstatus code: 200checked: Oct 19, 2026, 9:27 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Instagram normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 1604msstatus code: 200checked: Oct 19, 2026, 9:26 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Instagram 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 Instagram, 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 Instagram on September 16, 2026.

Recent probe events

No probe events on record yet for Instagram.

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

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

Full check history for Instagram: 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

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

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

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

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

How our checks compare with Instagram's stated SLA

At or above your target

Our checks of Instagram 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 Instagram'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.instagram.com/
primary
https://www.instagram.com/

What our check can and cannot see

A pass means the service's public web page loaded and answered normally. It does not show that the product, the API or sign-in behind it works; a page can load from a cache while the product is down.

Host checked: www.instagram.com

RealUptime is not affiliated with Instagram; the name identifies what we checked, and nothing here speaks for Instagram's own team. We send a single web request to Instagram from 10 regions on our own schedule and time the response. We do not see inside Instagram's systems, do not use an account or real transaction, and are not the same signal Instagram's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Instagram 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.