SORACOM logo

Is SORACOM down?

No reported issues

From status.soracom.io · checked 5 minutes ago · every 5 minutes

Get alerts for SORACOM

An email when it goes down, and when it’s back.

As of 12:50 UTC on 13 November 2026, SORACOM's status page reports no issues. Its last reported problem was on 12 November 2026: “SORACOM Air for セルラー (plan-US-max) によるSMSがご利用しづらい、または利用できない事象について”, issue, for 19 h 40 min from 05:35 UTC.

Last problem
12 Nov · 19 h 40 min
Problems, last 30 days
4 (1 critical)
Typical incident
11 h 10 min
Longest in 90 days
19 h 40 min · 12 Nov

Uptime

SORACOM, last 30 days

92.86 %

100%50%0%
Oct 15 Today

Biggest dip: SORACOM, 19.7 h of issue on Nov 12.

Incidents

Started in the last 7 days

2

210
SSMTWTToday

This week Week before

Latest: SORACOM, issue on Nov 12.

Recovery

Median time back online

13 h 50 min

19 h 40 min0
30 days ago Today

0 of 4 were over within an hour. Each dot is one incident; the dashed line is the median.

Components 86

All online

  • Others
Air for Cellular 31 parts
  • plan01s (Rendezvous point: Frankfurt)
  • plan01s (Rendezvous point: Oregon)
  • plan01s (Rendezvous point: Tokyo)
  • plan01s (Rendezvous point: Sydney)
  • planX1 (Rendezvous point: Frankfurt)
  • planX1 (Rendezvous point: Oregon)
  • planX1 (Rendezvous point: Tokyo)
  • planP1 (Rendezvous point: Frankfurt)
  • planP1 (Rendezvous point: Oregon)
  • planP1 (Rendezvous point: Tokyo)
  • planP1 (Rendezvous point: Sydney)
  • planX2 (Rendezvous point: Tokyo)
  • planX3 (Rendezvous point: Tokyo)
  • planX3 (Rendezvous point: Frankfurt)
  • planM1
  • planV1
  • planNT1
  • plan-US
  • plan-US-NA
  • plan-US-max
  • plan-NA1
  • plan-D
  • plan-K
  • plan-K2
  • plan-DU
  • plan-KM1
  • plan-MC
  • planXM1 (Rendezvous point: Frankfurt)
  • planXM1 (Rendezvous point: Oregon)
  • planXM1 (Rendezvous point: Tokyo)
  • Others
Air for Sigfox 2 parts
  • Global coverage
  • Japan coverage
Arc 5 parts
  • Global coverage (Rendezvous point: Frankfurt)
  • Global coverage (Rendezvous point: Oregon)
  • Global coverage (Rendezvous point: Tokyo)
  • Global coverage (Rendezvous point: Sydney)
  • Japan coverage
Beam 2 parts
  • Global Coverage
  • Japan Coverage
Canal 2 parts
  • Global Coverage
  • Japan coverage
Direct 2 parts
  • Global Coverage
  • Japan coverage
Door 2 parts
  • Global Coverage
  • Japan coverage
Endorse 2 parts
  • Global Coverage
  • Japan Coverage
Flux 2 parts
  • Global Coverage
  • Japan Coverage
Funk 2 parts
  • Global Coverage
  • Japan Coverage
Funnel 2 parts
  • Global Coverage
  • Japan Coverage
Gate 2 parts
  • Global Coverage
  • Japan coverage
Harvest Data 2 parts
  • Global Coverage
  • Japan Coverage
Harvest Files 2 parts
  • Global Coverage
  • Japan Coverage
Inventory 2 parts
  • Global Coverage
  • Japan Coverage
Junction 2 parts
  • Global Coverage
  • Japan coverage
Krypton 2 parts
  • Global Coverage
  • Japan Coverage
Lagoon 3 2 parts
  • Global coverage
  • Japan coverage
Napter 2 parts
  • Global Coverage
  • Japan Coverage
Orbit 2 parts
  • Global Coverage
  • Japan Coverage
Peek 2 parts
  • Global Coverage
  • Japan coverage
Query 2 parts
  • Global coverage
  • Japan coverage
Event Handler 2 parts
  • Global coverage
  • Japan coverage
API 2 parts
  • Global coverage
  • Japan coverage
User Console 2 parts
  • Global coverage
  • Japan coverage
Virtual Private Gateway 2 parts
  • Global coverage
  • Japan coverage
Soracom Cloud Camera Services (Migrated to https://status.sora-cam.com/) 1 part
  • Japan coverage

Last 90 days

5 incidents in 46 days tracked · no reported issues 94.4% of the time · typical incident 11 h 10 min

Aug 16 Today (UTC)

Recent incidents

Times in UTC

  1. Issue
    SORACOM Air for セルラー (plan-US-max) によるSMSがご利用しづらい、または利用できない事象について 19 h 40 min
  2. Critical
    SORACOM Air for セルラー (plan-US-max) による通信がご利用しづらい、または利用できない事象について 3 h 15 min
  3. Issue
    SORACOM Air for セルラー (planM1, planV1) サービス障害について 11 h 10 min
  4. Issue
    SORACOM Air for セルラー (planX1, plan01s) による通信がご利用しづらい、または利用できない事象について 16 h 30 min
  5. Issue
    SORACOM eSIM Profile サービス障害について 9 h 59 min
All incidents on status.soracom.io ↗

Where this comes from

Stackpulse reads SORACOM’s official status page at status.soracom.io every 5 minutes and keeps 90 days of what changed. We don’t test SORACOM ourselves, so a problem shows here once SORACOM reports it.

Stackpulse isn’t affiliated with SORACOM. Names and logos belong to their owners.

For agents and scripts

The same data as Markdown for AI agents, updated every 30 seconds. With Pro, the API and the MCP server give scripts and AI assistants every service and your own dashboards.