Fletcher Outage History
37 incidents recorded over the last 365 days, 35 of them resolved, 2 still open. 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 Fletcher Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 3, 2026 | BnBerry/ AirBNB reserveringen schieten nietDe reserveringen van BnBerry schieten sinds afgelopen weekend niet in. Graag reserveringen controleren en reserveringen handmatig in Shiji zetten. Prijzen kunnen uit het extranet gehaald worden + bijbehorende VCC's… | — | Investigating |
| Oct 21, 2026 | Veiligheidscontrole PHP websitesWe are continuing to work on a fix for this issue. | 20h 42m | Resolved |
| Oct 19, 2026 | BI Tool geeft een error bij het openen van een DashboardAlle datasets zijn weer bijgewerkt en de BI Tool is weer volledig online. | 3h 54m | Resolved |
| Oct 15, 2026 | Reserveringen Booking.com schieten niet in.Probleem is opgelost. Als het goed is zijn alle reserveringen er weer ingeschoten, welke er vanaf gistermiddag zijn gemaakt. | 15h 12m | Resolved |
| Oct 12, 2026 | Reservering data incompleet DWH2This incident has been resolved. | 54h 24m | Resolved |
| Sep 15, 2026 | AFAS Online inlogportal en Profit verminderd beschikbaarHet probleem bij AFAS is verholpen en de login werkt weer als vanouds. | 2h 36m | Resolved |
| Sep 10, 2026 | Profit opent nietThis incident has been resolved. | 2h 33m | Resolved |
| Aug 25, 2026 | Financiële mutaties incompleetThis incident has been resolved. | 4h 19m | Resolved |
| Aug 25, 2026 | Kassadata incompleet in oude data warehouseDoor een storing is de kassadata in het oude datawarehouse incompleet, we zijn dit met IT aan het herstellen. | — | Investigating |
| Aug 19, 2026 | BI Tool StoringDe restart is afgerond en de BI Tool is weer bereikbaar. | 2h 15m | Resolved |
| Aug 12, 2026 | Financiële mutaties incompleetThis incident has been resolved. | 116h 17m | Resolved |
| Jul 27, 2026 | Externe reserveringen schieten niet inReserveringen lijken kort na vorig bericht weer in te schieten. Graag handmatige reserveringen annuleren! | 12 min | Resolved |
| Jul 16, 2026 | [AFAS Online] Loginpiek veroorzaakt problemen bij het inloggenThis incident has been resolved. | 3h 36m | Resolved |
| Jul 14, 2026 | Reservations are not entering ShijiThe incident has been resolved. | 15h 10m | Resolved |
| Jul 8, 2026 | Externe reserveringen schieten niet in vanuit SiteminderReserveringen schieten weer in. Graag handmatige reserveringen annuleren + nieuwe reserveringen controleren. | 46 min | Resolved |
| Jul 6, 2026 | Seats not availableThis incident has been resolved. | 42 min | Resolved |
| Jun 26, 2026 | Bij het openen van een dossieritem op de klantportal van AFAS komt de melding: Het veld met Id 'SbId' bestaat niet in de collectieThis incident has been resolved. | 70h 56m | Resolved |
| May 21, 2026 | Incident Booking.com reservationsIssue has been solved by Booking. | 16h 11m | Resolved |
| May 21, 2026 | Verbindingsprobelemen Afas OnlineThis incident has been resolved. | 3h 59m | Resolved |
| May 5, 2026 | Shiji - Emergency / End of Day Rapporten worden niet verzondenHet automatisch versturen van de rapporten is weer hersteld. | 14h 6m | Resolved |
| May 5, 2026 | Shiji M&E Revenue in de BI ToolThis incident has been resolved. | 6h 16m | Resolved |
| May 5, 2026 | Externe reserveringen schieten niet inDe reserveringen schieten weer in! Graag de handmatige reserveringen annuleren, zodat de beschikbaarheid juist loopt. | 6h 32m | Resolved |
| Apr 7, 2026 | Siteminder reservations issueReservations coming from SiteMinder are expected to enter Shiji successfully. Please check if all reservations are in Shiji and to avoid double reservations. If not in Shiji, make sure you creaet the reservation… | 19h 39m | Resolved |
| Mar 10, 2026 | ictsupport@fletcher.nlAFAS heeft de oorzaak gevonden en het probleem opgelost. | 29 min | Resolved |
| Feb 25, 2026 | Foutmelding bij uitvoeren workflowactie: "Er is een onverwachte fout opgetreden."This incident has been resolved. | 17h 41m | Resolved |
| Feb 25, 2026 | Beperkte toegang T-schijf mappenInmiddels is er een herstelactie succesvol uitgevoerd. Mochten er nog T-schijf mappen niet zichtbaar zijn dient men af te melden en opnieuw aan te melden. | 2h 9m | Resolved |
| Jan 30, 2026 | Seats tijdelijk niet bereikbaarThis incident has been resolved. | 41 min | Resolved |
| Jan 19, 2026 | Server tijdelijk niet bereikbaarThis incident has been resolved. | 1h 4m | Resolved |
| Jan 13, 2026 | De Afas inlogportal is niet bereikbaar.This incident has been resolved. | 4h 2m | Resolved |
| Jan 12, 2026 | Revbot rate reccomendation werkt weer, maar de pick up geeft nog steeds problemen.This incident has been resolved. | 1010h 53m | Resolved |
| Dec 9, 2025 | AFAS Financiële Mutaties IncompleetThis incident has been resolved. | 46h 32m | Resolved |
| Nov 27, 2025 | Shiji Statistieken Data in DWH2 niet compleetThis incident has been resolved. | 5347h 50m | Resolved |
| Nov 24, 2025 | ictsupport@fletcher.nlThis incident has been resolved. | 1h 6m | Resolved |
| Nov 18, 2025 | Wereldwijde storing cloudflareThis incident has been resolved. | 73h 30m | Resolved |
| Nov 12, 2025 | Profit performance problemen / traagheid in ProfitThis incident has been resolved. | 51 min | Resolved |
| Nov 6, 2025 | Shiji issuesThis incident has been resolved. | 3h 17m | Resolved |
| Nov 5, 2025 | Shiji issuesThe issue has been resolved and everything should be functioning again. | 1h 34m | 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 Fletcher 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 Fletcher 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 Fletcher 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 Fletcher outage in this window ran 222d 19h, against a mean recovery of 8d 4h. If you depend on Fletcher 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.