Skip to content

Outage tracker

Particle: incident history

The last 24 hours in detail, Particle's declared incident record, and our regional check results beside it.

← Back to Particle's check readings

We started checking Particle on November 2, 2026, which is 6 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

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

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

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

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Particle's own status page declared. Below it, any public chatter we saw about Particle and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Particle's own status page declared. Three records side by side; none of them changes another.

Our probes, api
Unverified user reportsNo reports about Particle in the last 24 hours, which is not evidence that nothing is wrong.
Particle's status pageNo incident declared in the last 24 hours.

Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Particle's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention Particle next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Checks passing by region

Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionChecks passingProbes recorded
US-East100.00%587
US-West99.78%453
Europe100.00%410
Asia-Pacific100.00%249

Their declared record

Particle's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.

Infrastructure issue affecting Tachyon devicesMajor outage
Sep 21, 2026, 6:07 PM UTC to Sep 21, 2026, 9:45 PM UTC (3h 38m)resolved
their latest update (Sep 21, 2026, 9:45 PM UTC): This incident has been resolved.
Connectivity Disruption — Tachyon DevicesMinor incident
Sep 1, 2026, 8:48 PM UTC to Sep 1, 2026, 11:01 PM UTC (2h 14m)resolved
their latest update (Sep 1, 2026, 11:01 PM UTC): This incident has been resolved. All Tachyon devices have successfully reconnected and connectivity has been fully restored. Our team identified the root cause and implemented a fix, confirming full recovery across the affected fleet. No other Particle device type or SKU was af…
Connectivity Disruption — Tachyon DevicesMinor incident
Sep 1, 2026, 5:40 PM UTC to Sep 1, 2026, 6:55 PM UTC (1h 15m)resolved
their latest update (Sep 1, 2026, 6:55 PM UTC): This incident has been resolved. All Tachyon devices have successfully reconnected and connectivity has been fully restored. No other Particle device type or SKU was affected by this incident.
South African EtherSIM connectivityMinor incident
Jun 8, 2026, 12:16 PM UTC to Jul 14, 2026, 8:27 PM UTC (36d 8h)resolved
their latest update (Jul 14, 2026, 8:27 PM UTC): The issue is considered resolved. Affected devices will need to be reset or power cycled to resume connectivity.
Device connectivity instabilityMinor incident
May 21, 2026, 3:07 PM UTC to May 21, 2026, 8:17 PM UTC (5h 10m)resolved
their latest update (May 21, 2026, 8:17 PM UTC): The issue impacting cellular connectivity on our MVNO network has been resolved. Services have remained stable following recovery, and our teams have confirmed normal operation across affected systems.
Device connectivity instabilityMinor incident
May 15, 2026, 1:00 AM UTC to May 15, 2026, 1:26 AM UTC (27 min)resolved
their latest update (May 15, 2026, 1:26 AM UTC): This incident has been resolved.
Integration/Event stream instabilityMinor incident
May 6, 2026, 12:02 AM UTC to May 6, 2026, 12:41 AM UTC (39 min)resolved
their latest update (May 6, 2026, 12:41 AM UTC): Particle has deployed a fix, and services are back to baseline.
Ethersim connection instabilityMinor incident
May 1, 2026, 6:16 PM UTC to May 1, 2026, 9:01 PM UTC (2h 45m)resolved
their latest update (May 1, 2026, 9:01 PM UTC): Connectivity has recovered.
EtherSIM - Service degradationMinor incident
Mar 10, 2026, 5:00 PM UTC to Mar 10, 2026, 9:18 PM UTC (4h 18m)resolved
their latest update (Mar 10, 2026, 9:18 PM UTC): The issue was resolved
EtherSIM OutageAll systems operational
Mar 8, 2026, 8:15 AM UTC to Mar 8, 2026, 11:39 AM UTC (3h 24m)resolved
their latest update (Mar 8, 2026, 11:39 AM UTC): Connectivity has recovered to normal levels.

Showing the 10 most recent of 50 incidents Particle has declared in the history we hold.

These entries are Particle's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

Particle's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.

Full detail on what a probe does and does not prove is in the methodology page.