Heroku est-il en panne ?
PaaS historique pour applications web.
Gravité sur 90 jours
Sur les incidents publiés par le fournisseur. Maintenances exclues.
Interruptions sur 90 jours
Que faire si Heroku est en panne
Vérifier que ça ne vient pas de chez vous
Ouvrez un autre site. S'il se charge, votre connexion va bien.
Lire la source officielle
La page de statut de Heroku fait foi. C'est elle que nous relevons toutes les 5 minutes.
Page de statut officielle →Voir ce qui se dit en direct
Une panne apparaît souvent sur X avant que Heroku ne la publie.
Signalements « Heroku down » sur X →Savoir quand c'est rétabli
Plutôt que de recharger cette page, laissez votre adresse : l'alerte part dès la mise à jour.
Historique des incidents
Publié par Heroku
Resolved: Heroku Feature Degradation
<p>The upstream errors have been resolved, and normal operations have been restored. This incident is now resolved.</p>
Resolved: Heroku Feature Degradation
<p>Incident resolved.</p>
Resolved: Heroku Service Degradation
<p>Engineers have remediated the issue.</p>
Resolved: Heroku Retroactive Feature Degradation
<p>The issue is now resolved.</p>
Resolved: Heroku Feature Degradation
<p>We are aware of an issue that affected the ability to provision new Heroku Data add-ons. To remediate, we completed a rollback of a recent change and validated that all services have been restored.</p> <p>We apologize for how you and your business may have been affected by this incident. We will thoroughly investigate the incident, confirming the technical trigger, the underlying cause, and pr
Resolved: Heroku Retroactive Feature Degradation
<p>Between 11:01 UTC on August 6, 2026 and 13:10 UTC on August 6, 2026, we identified a performance issue affecting Heroku release phase deploys. During this time, some customers experienced delayed completion of release phase commands during deploys, with some remaining in an <code>release phase executing</code> state longer than expected. We have confirmed that the issue is resolved. We apologiz
Resolved: Heroku Service Disruption
<p>Incident resolved.</p>
Resolved: Heroku Retroactive Service Disruption
<p>We noted an issue that impacted Heroku Platform API services in all regions. Customers may have experienced broken pipeline API calls to ‘pipelines/:id/latest-builds’, and issues viewing the pipeline dashboard. We confirmed this incident was due to a recently deployed change, and have reverted this change to resolve the issue.</p> <p>We will continue to monitor the environment to ensure stabil
Resolved: Heroku Retroactive Feature Disruption
<p>The issue is now resolved.</p>
Resolved: Heroku Retroactive Feature Disruption
<p>The issue is now resolved.</p>
Resolved: Heroku Service Disruption
<p>We have successfully applied the fix to all remaining affected customers. Heroku databases and web applications are now fully operational for all customers. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.</p>
Resolved: Heroku Feature Disruption
<p>Upon further investigation, we've determined that the start time of impact is different than initially understood. We've revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.</p>
Resolved: Heroku Retroactive Feature Disruption
<p>The issue is now resolved.</p>
Resolved: Heroku Feature Disruption
<p>The issue is now resolved.</p>
Resolved: Heroku Retroactive Feature Degradation
<p>Customers using Heroku in the Common Runtime may have experienced intermittent dyno disruptions earlier today between 17:50 UTC and 20:24 UTC. The issue has been resolved after we disabled a related service and rolled back a recent change. We’re validating the update in lower environments and will continue monitoring for stability.</p>
Resolved: Heroku Platform Maintenance
<p>The maintenance is now complete. All functionality has now returned to normal.</p>
Resolved: Heroku Service Disruption
We’ve confirmed that the solution implemented to mitigate the issue causing the service disruption was successful. Engineers have observed that the service is stable and have resolved the incident. Customers should no longer see any impact. We will fully investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We apolo
Source officielle
Données issues de la page de statut publique de Heroku.
Page de statut officielleBadge pour votre site
Affichez le statut de Heroku chez vous. Mis à jour automatiquement, même adresse que cette page.
<a href="https://www.upstreamstatus.com/status/heroku"><img src="https://www.upstreamstatus.com/badge/heroku" width="280" height="64" alt="Heroku status" /></a>
Autres services Cloud & infrastructure
Questions fréquentes
Heroku est-il en panne actuellement ?
Au dernier relevé (2026-10-31 19:50 UTC), Heroku est en état « Opérationnel » d'après sa page de statut officielle. Aucun incident en cours n'est publié.
Quelle est la disponibilité de Heroku sur 90 jours ?
Heroku affiche 99.95 % de disponibilité sur les 90 derniers jours, avec 6 incidents publiés.
Comment être prévenu automatiquement d'une panne de Heroku ?
Créez une alerte gratuite sur Upstream Status : dès qu'un incident est publié sur la status page de Heroku, vous recevez un email (ou une notification Slack/webhook avec un plan payant).