Skip to content

Outage tracker / Particle

Is Particle down?

I'm having a problem

Vendor reports no incidentWhat Particle reports

Particle reports no incident on its status page.

As of the last successful poll, 2026-11-05 14:59 UTC.

Particle's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 3 minutes ago

Our checks of Particle pass from all 4 regions we check.

As of Nov 5, 2026, 3:07 PM UTC, RealUptime's checks of Particle passed in all 4 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 3:07 PM UTC
US-East1069 msChecks passing
US-West1621 msChecks passing
Europe842 msChecks passing
Asia-Pacific2715 msChecks passing
their status pagetheir claim, not our reading

Particle reports: All systems operational (“Service Under Maintenance”)

from Particle's own status page, checked Nov 5, 2026, 1:56 PM UTC
Particle's own status page shows no incident, and our checks of Particle pass right now.

Particle's own component breakdown, as they publish it

  • Cellular ConnectivityUnder maintenance
  • Ether SIMUnder maintenance
  • Particle WorkbenchOperational
  • store.particle.ioOperational
  • Particle CLIOperational
  • docs.particle.ioOperational
  • E Series LTE (E402), Boron LTE, B Series B402 SoM, Tracker T402 SoM, or Electron LTE (ELC402) (LTE Cat M1)Operational
  • Wi-Fi ConnectivityOperational
  • community.particle.ioOperational
  • B Series B523 SoM or Tracker T523 SoMOperational
  • REST APIOperational
  • build.particle.ioOperational
  • IntegrationsOperational
  • www.particle.ioOperational
  • Management ConsoleOperational
  • SIM state managementOperational
  • Tachyon CloudOperational
  • 2G/3G NorAmOperational
  • 2G/3G EMEAOperational
  • TachyonOperational

These are Particle's components, named and scored by Particle. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Particle's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Particle response time, by region

US-East
1.4sp95 · 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-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
US-West
2.1sp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 2.1s2026-11-03 UTC: p95 2.1s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5
Europe
1.5sp95 · 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-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.5s
Oct 7Oct 21Nov 5
Asia-Pacific
2.7sp95 · 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-11-02 UTC: p95 2.7s2026-11-03 UTC: p95 2.7s2026-11-04 UTC: p95 2.8s2026-11-05 UTC: p95 2.7s
Oct 7Oct 21Nov 5

Check your own site while you wait on Particle

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

Email me when Particle reports an incident on its status page, and again when it reports it resolved.

Get an email when Particle reports an incident

Email me when Particle reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Particle's own statement from its status page, with our regional reading beside it.

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
    Not monitored from this regionUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1069msstatus code: 400checked: Nov 5, 2026, 3:04 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Particle normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1621msstatus code: 400checked: Nov 5, 2026, 3:00 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Particle normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Not monitored from this regionParticle is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Canada
      Not monitored from this regionParticle is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionParticle is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Europe
    Not monitored from this regionEurope, UK
    • Europe
      Checks passinglatency: 842msstatus code: 400checked: Nov 5, 2026, 3:07 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Particle normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Not monitored from this regionParticle is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • Asia Pacific
    Not monitored from this regionAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 2715msstatus code: 400checked: Nov 5, 2026, 2:57 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Particle normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Not monitored from this regionParticle is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Australia
      Not monitored from this regionParticle is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say

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

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

Recent probe events

Infrastructure issue affecting Tachyon devices, 3h 38mdeclared on their status page2026-09-21
Connectivity Disruption — Tachyon Devices, 2h 14mdeclared on their status page2026-09-01
Connectivity Disruption — Tachyon Devices, 1h 15mdeclared on their status page2026-09-01
South African EtherSIM connectivity, 872h 11mdeclared on their status page2026-06-08
Device connectivity instability, 5h 10mdeclared on their status page2026-05-21
Device connectivity instability, 27mdeclared on their status page2026-05-15
Integration/Event stream instability, 39mdeclared on their status page2026-05-06
Ethersim connection instability, 2h 45mdeclared on their status page2026-05-01

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

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

Full check history for Particle: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Particle uptime by RealUptime's checksLive, from this page's own readings.
[![Particle uptime by RealUptime's checks](https://realuptime.io/outages/particle-io/badge.svg?days=30)](https://realuptime.io/outages/particle-io)
<a href="https://realuptime.io/outages/particle-io"><img src="https://realuptime.io/outages/particle-io/badge.svg?days=30" alt="Particle 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 Particle down?", https://realuptime.io/outages/particle-io. The readings change with every check, so give the date you read them.

What we check

primaryfunctional: live API
https://api.particle.io/v1/devices

What our check can and cannot see

A pass means the service's servers answered our request with the error they give a request that carries no account or valid input. It does not show that sign-in works or that any real request succeeds.

Host checked: api.particle.io

RealUptime is not affiliated with Particle; the name identifies what we checked, and nothing here speaks for Particle's own team. We send a single web request to Particle from 4 regions on our own schedule and time the response. We do not see inside Particle's systems, do not use an account or real transaction, and are not the same signal Particle's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Particle 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. Particle operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on November 2, 2026 (3 of 14 days so far, 1248 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.