Quick answer
Is CellMast down right now?
This page lists the parts of the CellMast service and the incidents we have recorded since the incident log started: none so far. A single dedicated port can go offline while the service works, because each port is one physical modem on a carrier network. If your port does not answer, rotate it once, then email [email protected]. Email replies within 12 hours, 7 days a week.
What do we check when you report a problem?
These are the parts we check first when a problem is reported. A failure on one does not mean the others are down.
| Component | What it does | Typical problem |
|---|---|---|
| Gateway (gw.cellmast.com) | Accepts HTTP on port 7777 and SOCKS5 on port 7778 | Connection refused for every port at once |
| Dedicated modems | One 4G/5G modem and SIM per port | One port offline or slow: coverage, carrier maintenance, power |
| Rotation API | Changes a port's IP by link or API call | 429 response when rotating more often than every 30 seconds (expected) |
| Rotating mobile pool | Per-GB carrier IPs with per-request or sticky rotation | Fewer IPs available in a small country |
| Client area and checkout | Top-ups, orders, credentials | Page error or slow loading |
| Payment detection | Credits a top-up after the network confirmations | Delay when a blockchain is congested |
Where will incidents be posted?
Incidents that affect many customers are written in the log below, with the start time, the end time in UTC and what was affected. Customers whose own port had a problem get a reply by email. A live status page with automatic checks is planned; this page will link to it when it exists.
Incident history
- 2026-10-13: incident log started. No incident recorded.
Why is there no uptime percentage here?
An uptime figure is only worth quoting when it comes from months of measurement with a stated method. CellMast has not published one yet, and will not print a number it has not measured. Carrier modems also fail one at a time, so a single site-wide percentage would hide what matters to you: whether your own port works.
How do I report a problem?
- Rotate the IP once with your rotation link and test again.
- Test with
curl -xfrom another network to rule out your own connection. - Email [email protected] with the port label, the time with its time zone and the error you see.
If the port cannot be fixed or moved, the refund policy applies.