Skip to content

Outage tracker / Instagram

Is Instagram down?

I'm having a problem

Operationalchecked moments ago

We reached Instagram from all 10 regions we check.

As of Oct 5, 2026, 8:16 PM UTC, Instagram 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 Instagram (since Aug 22, 2026).

Email me the next time we see Instagram go down

Measured by our own probes from ten regions, not Instagram'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, 8:16 PM UTC
US-East758 msOperational
US-West463 msOperational
Europe304 msOperational
Asia-Pacific489 msOperational
US-Central660 msOperational
Canada484 msOperational
UK284 msOperational
Southeast Asia737 msOperational
Australia574 msOperational
South America994 msOperational
their status pagetheir claim, not our reading

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

Instagram response time, by region

US-East
1.3sp95 · 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 641ms2026-09-07 UTC: p95 693ms2026-09-08 UTC: p95 708ms2026-09-09 UTC: p95 694ms2026-09-10 UTC: p95 713ms2026-09-11 UTC: p95 731ms2026-09-12 UTC: p95 811ms2026-09-13 UTC: p95 757ms2026-09-14 UTC: p95 851ms2026-09-15 UTC: p95 800ms2026-09-16 UTC: p95 965ms2026-09-17 UTC: p95 924ms2026-09-18 UTC: p95 838ms2026-09-19 UTC: p95 439ms2026-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.3s
Sep 6Sep 20Oct 5
US-West
490msp95 · 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 471ms2026-09-07 UTC: p95 465ms2026-09-08 UTC: p95 428ms2026-09-09 UTC: p95 283ms2026-09-10 UTC: p95 306ms2026-09-11 UTC: p95 253ms2026-09-12 UTC: p95 264ms2026-09-13 UTC: p95 290ms2026-09-14 UTC: p95 279ms2026-09-15 UTC: p95 510ms2026-09-16 UTC: p95 773ms2026-09-17 UTC: p95 676ms2026-09-18 UTC: p95 684ms2026-09-19 UTC: p95 697ms2026-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 490ms
Sep 6Sep 20Oct 5
Europe
793msp95 · 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 386ms2026-09-07 UTC: p95 402ms2026-09-08 UTC: p95 400ms2026-09-09 UTC: p95 382ms2026-09-10 UTC: p95 439ms2026-09-11 UTC: p95 489ms2026-09-12 UTC: p95 563ms2026-09-13 UTC: p95 462ms2026-09-14 UTC: p95 449ms2026-09-15 UTC: p95 486ms2026-09-16 UTC: p95 466ms2026-09-17 UTC: p95 392ms2026-09-18 UTC: p95 379ms2026-09-19 UTC: p95 374ms2026-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 793ms
Sep 6Sep 20Oct 5
Asia-Pacific
820msp95 · 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-06 UTC: p95 1.5s2026-09-07 UTC: p95 1.5s2026-09-08 UTC: p95 1.6s2026-09-09 UTC: p95 1.5s2026-09-10 UTC: p95 1.7s2026-09-11 UTC: p95 1.7s2026-09-12 UTC: p95 1.7s2026-09-13 UTC: p95 1.6s2026-09-14 UTC: p95 1.6s2026-09-15 UTC: p95 1.6s2026-09-16 UTC: p95 1.6s2026-09-17 UTC: p95 1.6s2026-09-18 UTC: p95 1.6s2026-09-19 UTC: p95 1.0s2026-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 820ms
Sep 6Sep 20Oct 5
US-Central
989msp95 · 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 874ms2026-09-07 UTC: p95 905ms2026-09-08 UTC: p95 858ms2026-09-09 UTC: p95 825ms2026-09-10 UTC: p95 815ms2026-09-11 UTC: p95 618ms2026-09-12 UTC: p95 567ms2026-09-13 UTC: p95 871ms2026-09-14 UTC: p95 928ms2026-09-15 UTC: p95 879ms2026-09-16 UTC: p95 863ms2026-09-17 UTC: p95 884ms2026-09-18 UTC: p95 835ms2026-09-19 UTC: p95 902ms2026-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 989ms
Sep 6Sep 20Oct 5
Canada
615msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 540ms2026-09-07 UTC: p95 420ms2026-09-08 UTC: p95 902ms2026-09-09 UTC: p95 820ms2026-09-10 UTC: p95 678ms2026-09-11 UTC: p95 697ms2026-09-12 UTC: p95 773ms2026-09-13 UTC: p95 777ms2026-09-14 UTC: p95 769ms2026-09-15 UTC: p95 776ms2026-09-16 UTC: p95 783ms2026-09-17 UTC: p95 808ms2026-09-18 UTC: p95 711ms2026-09-19 UTC: p95 424ms2026-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 615ms
Sep 6Sep 20Oct 5
UK
825msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 443ms2026-09-07 UTC: p95 568ms2026-09-08 UTC: p95 526ms2026-09-09 UTC: p95 389ms2026-09-10 UTC: p95 398ms2026-09-11 UTC: p95 472ms2026-09-12 UTC: p95 629ms2026-09-13 UTC: p95 429ms2026-09-14 UTC: p95 483ms2026-09-15 UTC: p95 361ms2026-09-16 UTC: p95 452ms2026-09-17 UTC: p95 397ms2026-09-18 UTC: p95 429ms2026-09-19 UTC: p95 399ms2026-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 825ms
Sep 6Sep 20Oct 5
Southeast Asia
1.2sp95 · 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 1.1s2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 1.3s2026-09-11 UTC: p95 1.3s2026-09-12 UTC: p95 1.0s2026-09-13 UTC: p95 1.0s2026-09-14 UTC: p95 1.0s2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.1s2026-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.2s
Sep 6Sep 20Oct 5
Australia
1.9sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. 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 1.5s2026-09-09 UTC: p95 1.6s2026-09-10 UTC: p95 1.4s2026-09-11 UTC: p95 1.5s2026-09-12 UTC: p95 1.3s2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 2.0s2026-09-19 UTC: p95 1.4s2026-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.9s
Sep 6Sep 20Oct 5
South America
1.2sp95 · 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-06 UTC: p95 1.0s2026-09-07 UTC: p95 999ms2026-09-08 UTC: p95 873ms2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 927ms2026-09-11 UTC: p95 913ms2026-09-12 UTC: p95 868ms2026-09-13 UTC: p95 961ms2026-09-14 UTC: p95 875ms2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 910ms2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 1.4s2026-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.2s
Sep 6Sep 20Oct 5

Is it Instagram, 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 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: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • AuthUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
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: 758msstatus code: 200checked: Oct 5, 2026, 8:15 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
      Operationallatency: 463msstatus code: 200checked: Oct 5, 2026, 8:16 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
      Operationallatency: 660msstatus code: 200checked: Oct 5, 2026, 8:16 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
      Operationallatency: 484msstatus code: 200checked: Oct 5, 2026, 8:13 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
    Operationallatency: 994msstatus code: 200checked: Oct 5, 2026, 8:16 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 304msstatus code: 200checked: Oct 5, 2026, 8:15 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
      Operationallatency: 284msstatus code: 200checked: Oct 5, 2026, 8:13 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 489msstatus code: 200checked: Oct 5, 2026, 8:16 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
      Operationallatency: 737msstatus code: 200checked: Oct 5, 2026, 8:15 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
      Operationallatency: 574msstatus code: 200checked: Oct 5, 2026, 8:13 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 outages

No outages on record yet for Instagram.

measured 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 measurements and Instagram's own claim at the time, side by side.

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

Put this badge in your README

Instagram uptime measured by RealUptimeLive, from this page's own readings.
[![Instagram uptime measured by RealUptime](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 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 Instagram's SLA implies, from our measurement

At or above your target

We measured none of downtime for Instagram 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 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/
RealUptime is not affiliated with Instagram; the name identifies what we measured, 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 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.