From 2:42 EDT to 3:47 EDT the GeoJson Outages API endpoint returned 500 errors in some cases.
A utility had unexpected characters in their geometry data. These characters were ingested and included in our dataset, but when that data was attempted to be returned by the GeoJson API our JSON formatter caught the bad characters and errored out, resulting in 500 errors for any GeoJson Outage API requests that included the effected utility.
This has been resolved, and we will be adding additional checks to our ingestion code to prevent this from happening again. We will also be adding a Malformed JSON check to our alerts, instead of waiting for this to get caught by an elevated 500 errors alert.