- Service Status
- /
- PebbleHost

Is PebbleHost Down?
- PebbleHost's status page
- Not available · we could not read it
- FlareWarden checks
- Website reachable · 12 of 12 regions · 175 ms
Right now
We could not read PebbleHost's status page, so the verdict rests on our checks. Check it yourself How we decide
FlareWarden checks
pebblehost.com from 12 regions · when you open this page (at most every 30 minutes), otherwise every 2 hours
- Regions up
- 12 of 12
- Response
- 175 ms
- Checked
By region
- Amsterdam reachable, 154 ms
- Chicago reachable, 103 ms
- Dallas reachable, 105 ms
- Frankfurt reachable, 72 ms
- Newark reachable, 77 ms
- Paris reachable, 94 ms
- San Jose reachable, 198 ms
- Singapore reachable, 281 ms
- Stockholm reachable, 94 ms
- Sydney reachable, 392 ms
- Tokyo reachable, 424 ms
- Toronto reachable, 110 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Amsterdam | 63 ms | 4 ms | 12 ms | 150 ms |
| Chicago | 49 ms | 1 ms | 7 ms | 102 ms |
| Dallas | 37 ms | 1 ms | 8 ms | 103 ms |
| Frankfurt | 18 ms | 2 ms | 8 ms | 69 ms |
| Newark | 45 ms | 3 ms | 9 ms | 74 ms |
| Paris | 18 ms | 2 ms | 9 ms | 92 ms |
| San Jose | 80 ms | 2 ms | 9 ms | 195 ms |
| Singapore | 9 ms | 2 ms | 13 ms | 278 ms |
| Stockholm | 30 ms | 2 ms | 8 ms | 91 ms |
| Sydney | 143 ms | 1 ms | 9 ms | 390 ms |
| Tokyo | 115 ms | 1 ms | 9 ms | 416 ms |
| Toronto | 44 ms | 2 ms | 6 ms | 107 ms |
History
PebbleHost website availability
Measured by FlareWarden · pebblehost.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 219ms
Last 30 days
49-day clean streakMeasured by FlareWarden's own checks of pebblehost.com from multiple regions every 2 hours. PebbleHost's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 49 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What PebbleHost does
PebbleHost is a UK-based hosting company, founded in 2017, best known for Minecraft server hosting. It also runs Hytale, Ark and Rust servers, Discord bot hosting in Java, NodeJS and Python, VPS, web hosting and dedicated servers. Customers manage servers through separate Game, Billing, VPS and Dedicated panels, with servers placed on nodes in Montreal, the UK, Sydney, Singapore, Miami, Hillsboro and Mumbai.
What an outage looks like
Most PebbleHost problems are local to one node rather than the whole company. Players cannot join a server, a Discord bot goes offline, or the server will not start, while other customers are unaffected. A wider fault shows as the Game Panel or Billing Panel failing to load. A panel reading Suspended - Offline is usually an unpaid invoice, an open ticket or a node migration, not an outage.
What to do about it
Open status.pebblehost.com and find the row for your node, such as AU103 or US188, or the Core rows for the Game Panel, Billing Panel and network. If the node is down, ask in PebbleHost's Discord support chat, which runs 24/7, or submit a ticket. If the downtime lasted over an hour, request SLA credit through a billing ticket within seven days.
Is it down for everyone, or just you?
If this page says PebbleHost is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
PebbleHost outage FAQ
Is PebbleHost down for everyone or just my server?
Does PebbleHost give compensation for downtime?
Why does my PebbleHost server say Suspended - Offline?
How do I contact PebbleHost support during an outage?
Does the PebbleHost status page show incident history?
How we measure this
- We request PebbleHost's public endpoint every 2 hours from Fly.io regions across six continents — the most recent check ran from 12 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their 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 PebbleHost publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of PebbleHost itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.
Get alerted when PebbleHost goes down
We check PebbleHost every 2 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring


