Latest updates and improvements to FourA
FourA's monitoring now supports custom alert thresholds per metric, so incidents get flagged faster. A new incident log tracks what happened, when it started, and when it recovered.
Your status dashboard now shows real-time CPU usage and request processing latency per endpoint. Spot bottlenecks at a glance instead of digging through logs.
When you contact support, we can replicate your exact dashboard view to see what you see. No credential sharing, no back-and-forth screenshots. Cuts resolution time for tricky API configs.
You can now delete API keys directly from the dashboard. Deleting a key invalidates it instantly across all endpoints and sends a confirmation email to the account owner.
Our Privacy Policy and Terms of Service are live. They're built into the sign-up flow, so you see exactly how we handle your data before creating an account.
You can create a FourA account with Google now. One click covers sign-up and Terms acceptance, then you're straight into your API keys and dashboard.
We added analytics to the Updates Portal, Blog, and Docs. Tracks aggregate engagement (most-visited sections, drop-off points) to help us prioritize what to build next. No personal data collected.
FourA's admin dashboard has a new Health page showing all services in one view: live metrics, uptime history bars, and per-instance details. Alert channels, severity thresholds, and alert history are all configurable from the same page.
When a service degrades or goes down, alerts fire immediately through email and Discord. Each alert includes severity details, affected services, and a direct link to the status page.
Two new sections on foura.ai: a blog for product updates and industry deep-dives, and a docs portal for API reference and integration guides. Both accessible through your FourA account.
Every monitored service now shows 30 days of uptime history. Each day is a color-coded bar: green for operational, yellow for degraded, red for outage. Hover for downtime details. A new Past Incidents section groups resolved incidents by date.
Every FourA service gets health-checked every 10 seconds. The system catches degradation in real time and creates incidents automatically. When a service recovers, the incident closes with a full timestamp for your uptime history.
HTTP scraping, browser sessions, and proxy requests each have their own rate limits now. Protects infrastructure during spikes and keeps resource allocation fair across customers. Rate-limited requests show up as a distinct outcome in your dashboard analytics.
A new settings interface lets you configure API endpoints with live performance indicators. See active connections, response times, and concurrency limits at a glance. Changes save in batch, so you don't have to update one by one.
You're looking at it. A changelog, status page, roadmap, and issue tracker in one place. Stay informed about what we're building, vote on features, and track incidents in real time.
