Last checked
Subscription billing and revenue management for SaaS businesses.
Experiencing an issue?
Chargebee est-il en panne?
Degraded performance
Share your experience to help others stay informed.
Official status checked
Chargebee is experiencing issues
Official provider statusOfficial incident active
Subject: Security Notice: No Impact from PHPshell Zero-Day Vulnerability — Chargebee is aware of the recently reported PHPshell zero-day vulnerability and has completed an initial assessment of its potential impact on our services. Chargebee does not use PHP in its customer-facing workflows. Based on our assessment, this vulnerability does not affect Chargebee’s services or customer integrations, and no action is required by our customers at this time. As an additional precaution, we are verifying with our subprocessors to confirm they are unaffected and to ensure appropriate safeguards remain in place across our service ecosystem. We will continue to monitor relevant security developments and provide updates if our assessment changes. If you have any questions, please contact Chargebee Support.
Official provider status0 individual report entries in the last 24 hours. This list includes legacy imports; external source aggregates are shown in the chart.
Official status observations, not measured service uptime.
Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.
| Incident name | Duration | StartedUTC | Acknowledged | Severity |
|---|---|---|---|---|
| 133h 48mOngoing | Yes | Unknown | ||
| 0m | Yes | Minor | ||
| 42h 53m | Yes | Minor | ||
| 0m | Yes | Minor | ||
| 2h | Yes | Major | ||
| 0m | Yes | Minor | ||
| 50m | Yes | Minor | ||
| 1h 4m | Yes | Minor |
Uptimus surveille Chargebee via sa source officielle et normalise les incidents, maintenances et composants en un état cohérent.
Cette page comprend actuellement 101 composants surveillés, 69 incidents, 56 maintenances et 17 jours d'historique connu.
Uptimus est un service indépendant sans affiliation avec Chargebee. Un état normal ne garantit pas que chaque utilisateur, appareil ou région soit épargné.
Recevez une alerte lorsque Chargebee ou un composant surveillé signale une panne majeure ou une perturbation critique. Les alertes peuvent être acheminées par les canaux activés dans votre espace, notamment l’e-mail, le push et les intégrations configurées. L’historique disponible contient 69 incidents indexés, donnant à chaque alerte un contexte au-delà de l’état actuel. Un incident récent indexé était « Subject: Security Notice: No Impact from PHPshell Zero-Day Vulnerability ».
Recevez des alertes sur les performances dégradées, les impacts partiels et les incidents qui ne constituent pas une panne complète. Uptimus suit actuellement 101 composants Chargebee: API (US), Accounting Services, Admin Console (US), Apple Store. Les alertes peuvent être acheminées par les canaux activés dans votre espace, notamment l’e-mail, le push et les intégrations configurées.
Planned work published by the official provider.
Checkout.com will undergo scheduled maintenance on Sep 25, 2026, from 00:00 UTC to 05:00 UTC. Please expect intermittent transaction timeouts and elevated decline rates during this 5-hour window.
Started 25 sept. 2026, 00:00 UTC · Resolved 25 sept. 2026, 05:00 UTC
The scheduled maintenance has been completed.
Started 19 sept. 2026, 12:30 UTC · Resolved 19 sept. 2026, 14:30 UTC
The scheduled maintenance has been completed.
Started 15 août 2026, 11:00 UTC · Resolved 15 août 2026, 15:00 UTC
The scheduled maintenance has been completed.
Started 27 juil. 2026, 02:30 UTC · Resolved 27 juil. 2026, 04:30 UTC
The scheduled maintenance has been completed.
Started 26 juil. 2026, 04:30 UTC · Resolved 26 juil. 2026, 09:30 UTC
The scheduled maintenance has been completed.
Started 25 juil. 2026, 04:30 UTC · Resolved 25 juil. 2026, 09:30 UTC
The scheduled maintenance has been completed.
Started 31 mai 2026, 04:30 UTC · Resolved 31 mai 2026, 09:30 UTC
The scheduled maintenance has been completed.
Started 30 mai 2026, 04:30 UTC · Resolved 30 mai 2026, 09:30 UTC
Les pages publiques de Downdetector s’appuient surtout sur les signalements des utilisateurs. Uptimus les associe aux incidents officiels, maintenances et états des composants lorsque le fournisseur les publie.
| Critères de comparaison | Uptimus | Downdetector |
|---|---|---|
| Signalements communautaires concernant Chargebee | Inclus | Inclus |
| Référence adaptative distinguant les cas isolés d’une panne étendue | Inclus | Inclus |
| Activité des signalements sur 24 heures et vue régionale | Inclus | Inclus |
| Un espace pour les sites, pages de statut, jeux Steam et apps et jeux Android | Inclus | Produit séparé |
| Alertes e-mail, push et webhook depuis le même espace | Inclus | Produit séparé |
| Mises à jour officielles et chronologie du statut de Chargebee | Inclus | Piloté par les signalements |
| État des composants et maintenances affichés séparément | Inclus | Limité sur les pages publiques |
The official status page for Chargebee reports normal operation. An unresolved official incident is listed: “Subject: Security Notice: No Impact from PHPshell Zero-Day Vulnerability”. 0 reports were recorded for Chargebee in the last 24 hours. Last official check: .
Partagez vos réflexions sur Chargebee
Soyez le premier à commenter!
Découvrez d'autres services populaires et leur état actuel
Évaluez ce service
Aucun avis pour le moment