
https://nitter.gq/t.co/iZnqwgGkCl from APImetrics (@apimetrics) - meaningful API quality and performance metrics for 1000s of critical APIs. No coding, no DevOps, no hassle
The internets
Joined December 2019
- Tweets518
- Following429
- Followers401
- Likes139
Hey @ENERGY @usdatagov we've been posting on our blog for weeks about the terrible performance of the Department of Energy's #API. What is going on over there??
81
Our CEO David O'Neill (@daveon) is attending the Financial Data Exchange Global Summit in Raleigh this week. And he's going to talk about how we build trust into API Ecosystems.
If you want to meet with David, please don't hesitate to reach out here – or to him directly!
In the US Govt APIs category, @CommerceGov dropped 30% from 8.22 (in the Green Zone) to 5.7 (in the Red Zone): increase in outliers with the standard deviation jumping massively (> 1000% on one, >300% on the other). It lit up like a Christmas tree on hubs.li/Q01ykb160!
41
In the Social collection, @soundcloud decreased by 11% from 8.98 to 8.01. This was owing to a short outage on 8 December that affected several endpoints with HTTP status code 504 Gateway Timeout being returned.
80
In Enterprise Messaging, @Zoom decreased from 8.21 to 7.31 . This was owing to a cluster of failures on 12/10 affecting several endpoints with HTTP status code 502 Bad Gateway + timeouts, all from the IBM Tokyo cloud location.
90
STARTING SOON! 5:05 pm, Louis Armand Ouest (level S3). Don't miss it! #apidays #apidaysglobal #apidaysparis
YIKES! @DeptVetAffairs in the US Government collection was in the Red Zone with a CASC score of 3.39. This was owing to an outage that started on 19 November (the previous week) and ended on 21 November with HTTP status code 503 Service Unavailable being returned.
In the UK Government collection, @DefraGovUK decreased by 13% from 9.27 to 8.11. This was owing to one endpoint that has been producing an extended and ongoing cluster of slow outliers (no failures) since 19 November.
In the Exchanges collection, @FTX_Official was again in the Red Zone with a CASC score of 0.59. 🤐😦😒
In Exchanges, @3commas_capital decreased by 24% from 8.78 (in the Green Zone) to 6.65 (in the Yellow Zone). This was owing to a cluster of slow outliers and failures that affected all endpoints on 7 November.
In the Exchanges collection, #FTX @FTX_Official was the worst performing API with a CASC score of 4.48 placing it in the Red Zone. Of the 10 FTX endpoints monitored, 8 started returning HTTP status code 503 Service Unavailable responses on 11/14.
1
In the Open Banking UK Sandboxes collection, @monzo dropped by 24% from 9.35 (in the Green Zone) to 7.06 (in the Yellow Zone) because of an outage on 1-2 November with calls being unable to connect to the endpoint.
In the Exchanges collection, @pancakefi decreased by 72% from 8.32 (in the Green Zone) to 2.36 (in the Red Zone). This was owing to an extended outage affecting all endpoints with many slow outliers and a high percentage of HTTP status code 500 Internal Server Error responses.
In the Open Banking UK Production collection, @Sainsburys_Bank decreased by 24% from 8.99 (in the Green Zone) to 6.86 (in the Yellow Zone). Whoops.
The OBIE Sandbox in the Open Banking UK Sandboxes collection is the Red Zone w/ a CASC score of 5.99. This a number of the endpoints for this sandbox API are quite slow and a number of outliers are observed periodically, presumably when a system reset occurs around midnight UTC.
In the Exchanges collection, @SimpleSwap_io decreased by 15% to 6.08 to 7.19 (both in the Yellow Zone). This was owing to an outage that affected all endpoints on 25 September with HTTP status code 504 Gateway Timeout responses being returned.



















