Reliability
Known Issues and Incident History
Follow confirmed service incidents, product issues and data-quality corrections from investigation through resolution. Each record shows customer impact, affected surfaces and the corrective action taken.
No active known issues are currently listed.
Incidents and corrections with a published resolution.
FXMD-2026-0729-FOMC
FOMC policy-rate WebSocket delivery delay
First observedThe July 29 Federal Open Market Committee target-rate update was detected after the official statement page had become available. This delayed the live policy-rate update and the lower-bound event was not included in the initial WebSocket delivery.
Customer impact
The upper-bound policy-rate event reached observed WebSocket clients approximately 16.5 seconds after the scheduled release. The related lower-bound value became available later through the REST changes feed.
Affected surfaces
- USD policy-rate WebSocket events
- FOMC target-range releases
Investigation and resolution details
Cause
Release detection used the Federal Reserve monetary-policy RSS feed as the primary signal. For this decision, the dated FOMC statement page was available before the corresponding RSS update. The three target-range values also needed a shared publication path to prevent a sibling value from being omitted from live delivery.
Resolution
FXMacroData now monitors the dated official FOMC statement directly for scheduled decisions, with RSS retained as a secondary recovery source. The upper bound, lower bound and midpoint are parsed from the same statement and published together as one release family.
Resolved
Timeline
-
Incident
The scheduled FOMC target-rate release was delivered late and the lower-bound event was absent from the initial WebSocket update.
-
Cause confirmed
Direct statement availability was confirmed to precede the RSS-based detection path used for this release.
-
Resolved
Direct statement monitoring and shared target-range publication were released.
- The official Federal Reserve statement remains the authoritative source.
- No customer account or API-key information was involved.
Release-calendar weekend timestamps
First observedSome generated release-calendar rows used weekend placeholder timestamps. Affected rows were normalized to the next business day.
Customer impact
Some release-calendar consumers could receive a non-business-day placeholder timestamp.
Affected surfaces
- Release Calendar API
- Affected surface: release-calendar responses.
Catalogue entries without published data
First observedSome catalogue responses included indicator entries before data was published for those entries. Catalogue responses now show only available published indicators.
Customer impact
Catalogue discovery could advertise an indicator before a usable published series was available.
Affected surfaces
- Data Catalogue API
- Affected surface: data-catalogue responses.
Policy-rate frequency label
First observedThe policy-rate catalogue label displayed a daily frequency where the customer-facing cadence should be tied to decision meetings.
Customer impact
The catalogue frequency label could misrepresent the cadence of policy-rate decisions.
Affected surfaces
- Data Catalogue metadata
- Affected surface: data-catalogue metadata.
Policy-rate announcement timestamps
First observedPolicy-rate announcement timestamps for AUD and NZD were corrected after a mismatch was identified in the published records.
Customer impact
Affected records could use an incorrect policy-decision announcement timestamp.
Affected surfaces
- Announcement History API
- Release Calendar API
- Affected surface: announcement history and release-calendar rows.
CAD documentation examples
First observedSome customer-facing examples used the non-canonical CAN code. Examples now use the canonical CAD code.
Customer impact
Developers copying the affected examples could use an unsupported currency code.
Affected surfaces
- API documentation
- Affected surface: API documentation examples.
Try a different search term or status filter.
Report a problem
Help us investigate quickly
Include the affected endpoint or product, the UTC time, expected and actual behaviour, and a safe request reference if available. Never include an API key, password or other credential.
How tracking works
Private reports, verified public updates
Report privately
Bug, data-quality, account and feature reports begin through the support channel.
Confirm and classify
We reproduce the report, identify affected services and determine whether a public record is appropriate.
Publish and resolve
Confirmed customer-impacting issues receive a public reference, status updates and a verified resolution.
Account, billing and security matters remain private. Feature requests are published only when they become confirmed product work.