top of page

How Our New API Health Page Stops Feasibility Delays

Writer: 28East
28East
5 days ago
2 min read

When a customer searches for fibre coverage on your site and the page keeps spinning, you lose sales.


The tricky part is figuring out why it’s slow. Is the issue on your side, or is a fibre network operator (FNO) having system trouble?


Without a clear overview of your fibre feasibility API status, your technical team wastes hours digging through code. To fix this, we launched our new API Service Health Status Page.


In this article, we share how it works and how it keeps your business moving.


Tracking Multiple Monitored Services in Real Time


Checking your own server is only half the battle. Because an ISP feasibility check relies on external networks, you also need to know if your partner systems are responding.


Our new page monitors 33 services simultaneously across the entire check pipeline:


  • Internal 28East APIs: Core systems like getcoverage, getexternal, and getfeasibility that power our address search, geocoding, and coverage tools.

  • Major FNOs and Telcos: Live status tracking for Openserve, MTN, Vodacom, Frogfoot, Herotel, and MetroFibre.

  • Wireless and Specialist Networks: Real-time connectivity for Comsol, Cybersmart, Rush Network, Skywire, Link Africa, FCC, and Neos Networks.

  • Aggregators and Enterprise Providers: Direct monitoring for Liquid Intelligent Technologies and ARC International.


What Each Status Means for Your Team


Whether you use 28East for website maps, call centre portals, or direct APIs, every status gives you instant context:


  • Operational: Everything is running normally. Feasibility checks are fast and smooth.

  • Degraded: Systems are slightly slower. Searches still work, but users might notice a small delay.

  • Severe latency: Systems are very slow, and our team is investigating. Support agents can check the page instantly instead of raising urgent IT tickets.

  • Down: A service is offline. If an internal 28East API drops, checks will fail. If a specific FNO drops, our system isolates it. Other provider coverage still loads normally, even when it skips the offline network.


Four Ways This Page Helps Your Business


We built this page to make daily operations easier for your team.


Here’s how:


  1. Spot root causes instantly: Hover over any latency spike on the interactive timeline to see whether the delay is caused by our system or a specific FNO.

  2. Track hourly performance: View detailed hourly stats, including uptime percentages, average speed, and error rates for every API.

  3. Easier audit reports: All status data feeds straight into your weekly and monthly feasibility reports for easy review.

  4. One technical hub: Get quick access to developer documentation and support links right alongside live system stats.


Take Control of Your Feasibility Pipeline


You should not have to spend time guessing why a coverage check is taking so long. Real-time visibility helps your team spot delays quickly and keep your business moving forward.


Bookmark our live API Service Health Status Page today or contact our team to see how our location tools can help your business grow.


 
 
 

Comments


bottom of page