Contentful: Location Fields Not Rendered Correctly in APIs
Timeline of updates
- resolved
We released a version of our API software that caused location fields - composed of latitude and longitude - to not be returned correctly some API responses. Following user reports this release was rolled back 70 minutes after deployment and API responses went back to the correct values.
From Contentful’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on www.contentfulstatus.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Contentful, started 2016-05-03 12:10 UTC, resolved after 0 min, 1 update(s).
- Title
- Location Fields Not Rendered Correctly in APIs
- Vendor
- Contentful
- Date
- URL
- https://rewindex.com/company/contentful/incidents/6jbvhyfxlt3y
Contentful profileRecent Contentful incidentsAll outages on May 3, 2016Contentful in May 2016MarkdownJSON