Skip to main content

Is Mapbox Down?

No — Mapbox is up

Reachable from all 8 checked regions

Average response time: 310ms

Last checked · checks run every 6 hours

Official status page: https://status.mapbox.com

Mapbox uptime

100%
Last 7 days
—
Last 30 days
—
Last 90 days
—
Avg response, 30 days

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

30-day history

5-day clean streak
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: no data
Aug 16: no data
Aug 17: no data
Aug 18: no data
Aug 19: 100.00% uptime, 16 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 32 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 32 checks
Aug 24: no data
Jul 26 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
147ms
DNS 20ms TCP 2ms TLS 6ms TTFB 134ms
arn
256ms
DNS 26ms TCP 10ms TLS 23ms TTFB 209ms
bom
1243ms
DNS 3ms TCP 135ms TLS 275ms TTFB 679ms
cdg
177ms
DNS 28ms TCP 2ms TLS 8ms TTFB 163ms
dfw
211ms
DNS 49ms TCP 0ms TLS 4ms TTFB 201ms
ewr
160ms
DNS 8ms TCP 6ms TLS 16ms TTFB 131ms
fra
161ms
DNS 12ms TCP 1ms TLS 5ms TTFB 151ms
syd
1696ms
DNS 53ms TCP 179ms TLS 365ms TTFB 882ms
yyz
131ms
DNS 29ms TCP 1ms TLS 4ms TTFB 124ms

What Mapbox does

Mapbox supplies maps, navigation, search and location data to applications through APIs and SDKs. Developers embed its map tiles with GL JS on the web or the mobile SDKs, and call its geocoding, directions and traffic services. Any product that shows a map, plans a route or turns an address into coordinates may depend on it.

What an outage looks like

Maps render as blank grey panels where tiles should be, or load partially with missing areas. Geocoding and search return errors, so address lookup fails while the rest of the page works. Directions calls time out and routes never draw. Mobile apps built on the SDKs show the same empty map. Mapbox Studio may fail to open or save styles.

What to do about it

status.mapbox.com lists API, Search, Imagery, Geodata, Studio, GL JS, GL Native, the Mobile SDKs, Accounts, Telemetry and Mapbox Traffic Data separately, so a broken search box is easy to separate from broken tiles. Degrade the interface on purpose: show a list or the address as text instead of an empty panel, which reads to users as your application being broken.

Is it down for everyone, or just you?

If this page says Mapbox 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

AWS
AWS
Cloudflare
Cloudflare
A
Algolia
F
FlightAware

Mapbox outage FAQ

Our map is grey and empty. Is Mapbox down?
Check the API and Imagery components, which cover tile delivery. A grey panel usually means tile requests are failing rather than the map library failing to load. If the status page is clear, look at your access token, any URL restrictions on it, and whether you have passed a usage limit, since all three produce exactly the same empty result.
Search fails but the map still renders. How?
Search and geocoding are a separate component from tile delivery and they fail independently. The map you can see comes from tile endpoints, while address lookup goes to the Search API. Read the component list rather than the overall indicator, and consider hiding the search box during an incident so users are not left typing into something that cannot answer.
Do the mobile SDKs go down with the web map?
Not always. Mapbox lists GL JS, GL Native and the Mobile SDKs as distinct components, and the platforms can differ. They do share the underlying tile and API services, so an incident at that layer reaches both. Testing the same view on web and on mobile is a fast way to tell a platform-specific problem from a service-wide one.
What should our app show while maps are unavailable?
Show the underlying information in another form. An address, a list of stops or a static fallback image keeps the screen useful, where a blank grey rectangle reads as your application being broken. Add a short line saying maps are temporarily unavailable, and keep dependent actions such as confirming an address working without the map.

How we measure this

  • We request Mapbox'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 Mapbox 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 Mapbox 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