FYERS Outage History
9 incidents recorded over the last 365 days, 9 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded FYERS Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 29, 2026 | Realtime feeds and order placement issue for BSE F&O and BSE CMDue to an intermittent issue at the BSE exchange, order placement was impacted for a few clients in the BSE F&O and BSE CM segments. The issue was observed during the following time periods: 1. 12:08:53 PM to 12:09:21… | 0 min | Resolved |
| Oct 6, 2026 | Real time data and Order placement issue on SENSEX 72400 PE and 73000 PE contractThis incident has been resolved. | 9 min | Resolved |
| Sep 15, 2026 | BSE F&O Segment Disruption – Exchange-Side IssueWe are experiencing issues with live feed updates and order placement for certain contracts in the BSE F&O segment due to an exchange-side issue. We are monitoring the situation and will share an update once it is… | 4 min | Resolved |
| Aug 10, 2026 | Order placement issue on SENSEX 78700 CE contractThis incident has been resolved. | 12 min | Resolved |
| Jul 29, 2026 | Feeds unavailable for Sensex 77500 strikeThis incident has been resolved. | 12 min | Resolved |
| Mar 9, 2026 | Commodities Order Placement Issues - MCXThis incident has been resolved. | 4h 16m | Resolved |
| Dec 22, 2025 | Intermittent data issue with charts and options chainThis incident has been resolved. | 21 min | Resolved |
| Dec 8, 2025 | Sensex Live Tick Disruption – Exchange-Side IssueThis incident has been resolved. | 53 min | Resolved |
| Dec 5, 2025 | Service Disruption Due to Global Cloudflare OutageThe issue has been resolved by Cloudflare team | 21 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next FYERS incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This FYERS Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before FYERS acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single FYERS outage in this window ran 4h 16m, against a mean recovery of 43 min. If you depend on FYERS in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.