Status
Platform status.
Always transparent.
Monitor the health of every AlleForge service in real time, and stay informed about incidents, maintenance, and platform availability.
Platform status
Everything running smoothly
All Systems Operational
Operational
Healthy
Updated a few moments ago
Service health
Every service, monitored
Workspace
Core request building and testing environment.
API Testing
Send requests and inspect responses in real time.
Documentation
Guides, references, and quick starts.
Authentication
Login, sessions, and token issuance.
Collaboration
Live cursors, comments, and shared workspaces.
API Reference
Auto-generated, always-synced reference docs.
Mock Server
Simulate API responses before the backend exists.
Monitoring
Uptime and performance tracking for endpoints.
AlleForge Agent
AI-assisted request drafting and debugging.
Live infrastructure
Every layer, healthy
A simplified view of the path your requests take through AlleForge.
Browser
OperationalYour request leaves the workspace.
Edge
OperationalRouted through the nearest edge node.
API
OperationalHandled by the AlleForge API layer.
Workspace
OperationalMatched against your saved collection.
Database
OperationalReads and writes committed safely.
Storage
OperationalAttachments and history persisted.
Agent
OperationalAvailable for AI-assisted requests.
Incident history
Transparent, even when things break
Every incident, resolved and documented. Click any entry for the full story.
Scheduled maintenance
Planned work, communicated early
No maintenance scheduled
There’s nothing planned right now. If that changes, it will show up here well before it happens. Seeing something odd that isn’t reflected here? Let us know.
What a maintenance window looks like
Workspace database upgrade
Expected impact: brief read-only mode for workspace history during the window — testing and requests are unaffected.
Incident lifecycle
How we handle every incident
- 01
Issue Detected
Automated monitoring or a report flags something abnormal.
- 02
Investigation
The on-call team starts digging into logs and metrics.
- 03
Root Cause
The underlying cause is identified and confirmed.
- 04
Fix
A fix is developed, tested, and rolled out.
- 05
Monitoring
The team watches closely to confirm the fix holds under real traffic.
- 06
Resolved
The incident is closed and documented publicly.
Stay informed
Subscribe to status updates
Get notified the moment something changes — pick whichever channel fits your workflow.
RSS Feed
Subscribe with any feed reader.
Webhook
Push incidents into your own systems.
Slack
Get alerts in a dedicated channel.
Discord
Status updates in your server.
Reliability principles
Transparency first.
Continuous monitoring.
Fast incident response.
Clear communication.
Trust you can verify.
Frequently asked
Questions about our status
Service health is monitored continuously, and this page reflects the current state in real time — no manual refresh needed.
Enter your email above for status emails, or use the RSS feed if you'd rather pull updates into your own reader.
Scheduled maintenance is posted here in advance with the affected service, expected duration, and impact — so there are no surprises.
Each incident gets a public entry the moment it starts, updated as we learn more, and closed out with a resolution summary.
Webhook notifications are coming soon, so you'll be able to pipe status changes directly into your own alerting systems.
Build with confidence.
A platform you can trust, monitored around the clock and transparent when it matters most.