Skip to main content

Is Arduino Down?

No — Arduino is up

Reachable from all 8 checked regions

Average response time: 59ms

Last checked · checks run every 6 hours

Official status page: https://status.arduino.cc

Arduino uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
42ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 9 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

9-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: no data
Aug 9: no data
Aug 10: no data
Aug 11: no data
Aug 12: no data
Aug 13: no data
Aug 14: no data
Aug 15: 100.00% uptime, 16 checks
Aug 16: 100.00% uptime, 32 checks
Aug 17: 100.00% uptime, 40 checks
Aug 18: 100.00% uptime, 32 checks
Aug 19: 100.00% uptime, 40 checks
Aug 20: 100.00% uptime, 24 checks
Aug 21: 100.00% uptime, 32 checks
Aug 22: 100.00% uptime, 26 checks
Aug 23: 100.00% uptime, 32 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
56ms
DNS 1ms TCP 2ms TLS 15ms TTFB 43ms
arn
95ms
DNS 1ms TCP 1ms TLS 13ms TTFB 86ms
bom
55ms
DNS 0ms TCP 3ms TLS 12ms TTFB 39ms
cdg
39ms
DNS 0ms TCP 2ms TLS 8ms TTFB 28ms
dfw
49ms
DNS 0ms TCP 1ms TLS 12ms TTFB 38ms
ewr
47ms
DNS 1ms TCP 2ms TLS 9ms TTFB 33ms
fra
57ms
DNS 0ms TCP 1ms TLS 14ms TTFB 49ms
gru
77ms
DNS 0ms TCP 3ms TLS 10ms TTFB 36ms
yyz
32ms
DNS 0ms TCP 1ms TLS 6ms TTFB 23ms

What Arduino does

Arduino is the open-source electronics platform used across hobby projects, classrooms and industrial prototyping. Alongside the boards, Arduino Cloud is an online service for writing sketches in a browser, provisioning devices over Wi-Fi, LoRa, Ethernet or cellular, syncing Cloud Variables to dashboards and pushing over-the-air firmware updates, which makes it a live dependency for deployed hardware rather than only a development convenience.

What an outage looks like

Devices show as offline in the Cloud dashboard while the hardware itself is running fine, because the fault is in the link rather than the board. Dashboard widgets freeze on their last value as Cloud Variables stop syncing. The browser Editor fails to compile or upload sketches, over-the-air updates will not start, and REST API calls from scripts and integrations return errors.

What to do about it

Check status.arduino.cc, which tracks Arduino Cloud, Editor, IoT Cloud UI and Dashboards, Device connectivity, API Requests, Historical data ingestion, Authentication, Integrations and the EdgeImpulse machine learning tools as separate components. Device connectivity can fail while the Editor holds, and the reverse. Sketches already flashed to a board keep running their local logic, so hardware doing standalone work is unaffected by a Cloud fault.

Is it down for everyone, or just you?

If this page says Arduino is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Arduino outage FAQ

Is Arduino Cloud down for everyone or just me?
Check status.arduino.cc against the per-region measurements on this page. Arduino tracks Device connectivity separately from the IoT Cloud UI, so a dashboard that loads while boards stay offline is a real and common split rather than a contradiction. If both the status page and our regions look clean, the more likely cause is the network the device sits on, particularly on Wi-Fi boards behind a restrictive firewall.
Does my Arduino board stop working if Arduino Cloud is down?
No. A sketch already flashed to a board runs from the board's own memory and keeps executing its local logic through a Cloud outage. What stops is everything that depends on the link: Cloud Variables no longer sync, dashboards stop updating, triggers and scheduled tasks that rely on the service do not fire, and you cannot push new firmware over the air until connectivity returns.
Will I lose sensor data recorded during an outage?
Historical data ingestion is a separate component on Arduino's status page, so data collection can fail while other parts of the service work. Readings a device could not deliver are not queued indefinitely by the platform, so treat a long ingestion outage as a gap in the series. If the data matters, log it locally on the device or to an SD card rather than relying on the Cloud as the only store.
Can I still write and upload code during an Arduino Cloud outage?
Yes, if you use the desktop IDE rather than the browser Editor. The Editor and the Cloud Agent that connects it to a board over USB depend on the service, so a browser upload fails during an outage. The offline IDE compiles and flashes locally over USB with no service involved, which makes it the reliable fallback when Arduino Cloud is unavailable.

How we measure this

  • We request Arduino's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Arduino publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Arduino goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required