BitLaunch logo

Is BitLaunch down?

No reported issues

From status.bitlaunch.io · checked 2 minutes ago · every 5 minutes

Get alerts for BitLaunch

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

As of 03:28 UTC on 12 November 2026, BitLaunch's status page reports no issues. Its last reported problem was on 31 October 2026: “Partially Degraded Service”, issue, for 2 days from 17:54 UTC.

Last problem
31 Oct · 2 days
Problems, last 30 days
1
Typical incident
2 days
Longest in 90 days
2 days · 31 Oct

Uptime

BitLaunch, last 30 days

86.17 %

100%50%0%
Oct 14 Today

Biggest dip: BitLaunch, 48.2 h of issue on Oct 31.

Incidents

Started in the last 7 days

0

210
FSSMTWToday

This week Week before

No incidents this week. The last one: BitLaunch, issue on Oct 31.

Recovery

Median time back online

48 h 10 min

2 days0
30 days ago Today

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

Components 43

All online

  • Web App
  • API
  • Payments
BitLaunch Servers 8 parts
  • AMS1
  • AMS3
  • LON1
  • LAX1
  • CHI1
  • DAL1
  • BUC1
  • SGP1
Vultr 1 part
  • Vultr status can be found at https://status.vultr.com/
Linode 13 parts
  • Linode
  • Linode Linode Manager and API
  • Linode US-East (Newark)
  • Linode US-Central (Dallas)
  • Linode US-West (Fremont)
  • Linode US-Southeast (Atlanta)
  • Linode CA-Central (Toronto)
  • Linode EU-West (London)
  • Linode EU-Central (Frankfurt)
  • Linode AP-South (Singapore)
  • Linode AP-Northeast-2 (Tokyo 2)
  • Linode AP-West (Mumbai)
  • Linode AP-Southeast (Sydney)
DigitalOcean 18 parts
  • DigitalOcean Global
  • DigitalOcean AMS2
  • DigitalOcean AMS3
  • DigitalOcean ATL1
  • DigitalOcean BLR1
  • DigitalOcean FRA1
  • DigitalOcean LON1
  • DigitalOcean MKC1
  • DigitalOcean NYC1
  • DigitalOcean NYC2
  • DigitalOcean NYC3
  • DigitalOcean RIC1
  • DigitalOcean SFO1
  • DigitalOcean SFO2
  • DigitalOcean SFO3
  • DigitalOcean SGP1
  • DigitalOcean SYD1
  • DigitalOcean TOR1

Last 90 days

2 incidents in 48 days tracked · no reported issues 95.7% of the time · typical incident 2 days

Aug 15 Today (UTC)

Recent incidents

Times in UTC

  1. Maintenance
    USA maintenance - Los Angeles, Chicago, Dallas 7 h 59 min
  2. Maintenance
    Software Upgrade London 6 h 10 min
  3. Maintenance
    Software Upgrade London 1 h 4 min
  4. Maintenance
    Hardware Upgrade in Amsterdam 1 and 1 more 4 h
  5. Maintenance
    Ongoing Maintenance Amsterdamn 3 and 1 more 1 h
  6. Maintenance
    AMS3 upstream maintenance scheduled 15 min
  7. Issue
    Partially Degraded Service 2 days
  8. Maintenance
    Service Under Maintenance 1 h 26 min
  9. Maintenance
    Important Host Maintenance 7 h 30 min
  10. Maintenance
    Service Under Maintenance 19 h 6 min
All incidents on status.bitlaunch.io ↗

Where this comes from

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

Stackpulse isn’t affiliated with BitLaunch. 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.