STATUS OF SERVICES
Platform status
Live health for the Slammed.st control plane, proxy nodes, Layer 7 handlers, and testing network — check here before major authorized capacity windows.
Network throughput
2026 · requests processed
Operational Degraded Outage Maintenance
Platform
8 services| Name | Availability · last 90d | Response | 24h | |
|---|---|---|---|---|
|
Domain
slammed.st edge & TLS
|
|
18.5 ms | ||
|
Control Plane API
Hub, start/stop, automations
|
|
42.4 ms | ||
|
Dashboard & Hub
Workspace UI
|
|
36.8 ms | ||
|
Authentication
Sessions and sign-in
|
|
29.8 ms | ||
|
Billing & Payments
Crypto checkout and wallet
|
|
64.4 ms | ||
|
Support Chat
Live inbox and Telegram bridge
|
|
50.7 ms | ||
|
Target Verification
Ownership checks
|
|
48.6 ms | ||
|
DNS / Anycast Edge
Global resolver path
|
|
21.9 ms |
Proxy Nodes
4 services| Name | Availability · last 90d | Response | 24h | |
|---|---|---|---|---|
|
Proxy Node FR
Paris, France
|
|
23.6 ms | ||
|
Proxy Node CN
Hong Kong / CN egress
|
|
57.1 ms | ||
|
Proxy Node IL
Tel Aviv, Israel
|
|
33.1 ms | ||
|
Proxy Node RU
Moscow, Russia
|
|
36.7 ms |
Layer7 Handlers
7 services| Name | Availability · last 90d | Response | 24h | |
|---|---|---|---|---|
|
Layer7 Handler #1
Application traffic cluster
|
|
46.0 ms | ||
|
Layer7 Handler #2
Application traffic cluster
|
|
43.9 ms | ||
|
Layer7 Handler #3
Application traffic cluster
|
|
54.0 ms | ||
|
Layer7 Handler #4
Application traffic cluster
|
|
40.5 ms | ||
|
Layer7 Handler #5
Application traffic cluster
|
|
48.8 ms | ||
|
Layer7 Handler #6
Application traffic cluster
|
|
58.0 ms | ||
|
Layer7 Handler #7
Application traffic cluster
|
|
69.0 ms |
IoT Network Handlers
4 services| Name | Availability · last 90d | Response | 24h | |
|---|---|---|---|---|
|
IoT Network Handler #1
IoT mesh cluster
|
|
27.1 ms | ||
|
IoT Network Handler #2
IoT mesh cluster
|
|
29.8 ms | ||
|
IoT Network Handler #3
IoT mesh cluster
|
|
28.2 ms | ||
|
IoT Network Handler #4
IoT mesh cluster
|
|
34.6 ms |
Spoofed Handlers
4 services| Name | Availability · last 90d | Response | 24h | |
|---|---|---|---|---|
|
Spoofed Handler #1
Spoofed traffic cluster
|
|
33.5 ms | ||
|
Spoofed Handler #2
Spoofed traffic cluster
|
|
37.3 ms | ||
|
Spoofed Handler #3
Spoofed traffic cluster
|
|
38.8 ms | ||
|
Spoofed Handler #4
Spoofed traffic cluster
|
|
34.6 ms |
Incident history
Resolved events from the last 90 days.
Elevated error rate on Layer7 Handler #6
A subset of application workers returned 5xx responses for about 96 minutes. Traffic was drained to neighboring handlers while the pool restarted.
Read report →Elevated latency on Proxy Node CN
Hong Kong egress RTT climbed during a regional transit flap. Remaining proxy nodes absorbed the shift automatically.
Read report →Delayed crypto payment confirmations
Wallet credits landed later than usual after a provider API slowdown. Balances were not lost; pending payments caught up once webhooks resumed.
Read report →Packet loss on IoT Network Handler #2
A mesh coordinator dropped a fraction of datagrams after a rolling restart. Handlers #1, #3 and #4 were not affected.
Read report →Intermittent DNS probe timeouts
A subset of anycast PoPs answered slowly during a route withdrawal. Domain TLS termination stayed up.
Read report →Brief packet loss on Layer7 Handler #3
Workers in one region restarted after a kernel update. Other Layer7 handlers were unaffected.
Read report →Spoofed Handler #3 capacity reduced
Health checks marked a subset of nodes stale. The pool was rebuilt and the handler returned to full capacity.
Read report →Support chat delivery lag
Live chat messages queued longer than usual while the bridge to operator inboxes caught up. No conversations were lost.
Read report →