Los Angeles, United States
Degraded performance
38 dni temu
Last checked
Bitbucket status
Git-based code collaboration and CI/CD tool for teams using Jira.
Experiencing an issue?
Czy Bitbucket nie działa?
Operational
Source: official status page
Having issues with Bitbucket?
Share your experience to help others stay informed.
Bitbucket service health graph
Service status and report activity over the last 24 hours, in 15-minute intervals. Early warnings and official incidents are shown separately.
Bitbucket activity
Loading reports… · Last 24 hours
Download
- No problems detected
- Possible problems
- Problems detected
- Early warning
- Official incident
Tap a bar to keep its details open. With the chart focused, use Left and Right to move between intervals, Home or End to jump, and Escape to close. Full data is available in the table below.
View chart data
| Start | End | Reports | Status |
|---|
Latest activity
Last 24 hoursOfficial status checked
All systems operational
Official provider status
Bitbucket outage reports
0 outage reports in the last 24 hours.
30 reports loaded
Archive · older than 24 hours
Chicago, United States
Degraded performance
38 dni temu
San Jose, United States
Major outage
31 lip, 12:25 – 38 dni temu
View 2 reports
Major outage
Major outage
Boardman, United States
Degraded performance
38 dni temu
Reston, United States
Major outage
31 lip, 12:25 – 38 dni temu
View 2 reports
Major outage
Major outage
Loudoun County, United States
Major outage
31 lip, 12:25 – 38 dni temu
View 4 reports
Major outage
Major outage
Major outage
Major outage
Columbus, United States
Major outage
31 lip, 12:25 – 38 dni temu
View 2 reports
Major outage
Major outage
New York, United States
Degraded performance
38 dni temu
Loudoun County, United States
Degraded performance
31 lip, 12:25 – 38 dni temu
View 2 reports
Degraded performance
Degraded performance
Chicago, United States
Major outage
38 dni temu
Boardman, United States
Major outage
38 dni temu
New York, United States
Major outage
38 dni temu
Los Angeles, United States
Major outage
38 dni temu
Chicago, United States
Major outage
38 dni temu
Boardman, United States
Major outage
38 dni temu
New York, United States
Major outage
38 dni temu
Los Angeles, United States
Major outage
38 dni temu
Loudoun County, United States
Major outage
38 dni temu
New York, United States
Degraded performance
38 dni temu
San Jose, United States
Major outage
38 dni temu
Los Angeles, United States
Major outage
38 dni temu
Boardman, United States
Major outage
38 dni temu
Columbus, United States
Major outage
38 dni temu
Similar reports from the same location are grouped in 5-minute windows. Counts reflect the reports shown.
Bitbucket status history
Official status observations, not measured service uptime.
Last 60 daysDaily history
Loading history…
- Działa
- Problemy
- Awaria
- Konserwacja
- Brak danych
Bitbucket components
Bitbucket incident history
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 |
|---|---|---|---|---|
| 2h 29m | Yes | Unknown | ||
| 1h 26m | Yes | Minor | ||
| 1h 45m | Yes | Critical | ||
| 18h 14m | Yes | Minor | ||
| 22m | Yes | Minor | ||
| 2h 48m | Yes | Minor | ||
| 3h 46m | Yes | Minor | ||
| 2h 27m | Yes | Critical |
Dyskusja społeczności
Podziel się swoimi przemyśleniami na temat Bitbucket
@Andres·Guest
Bitbucket is stopping me from pushing changes, it returns 500 error
Guest
pipeline not working today
Guest
SSH keys are broken for auth
Guest
Pipeline builds are stuck on the Queued status.
Guest
Pipelines are stuck on the Queued status for us.
Guest
Pipelines appear to be stuck in running queue'd steps
Guest
Seems to be down, lots of latency and "System Error" when you stop your slow pipeline.
Guest
One last reason pushes me to Github.
O monitorowaniu Bitbucket w Uptimus
Uptimus monitoruje Bitbucket przez oficjalne źródło i normalizuje incydenty, konserwacje oraz komponenty do jednego spójnego statusu.
Strona zawiera obecnie 13 komponentów, 51 incydentów, 51 konserwacji i 5 dni znanej historii.
Uptimus jest niezależny i nie jest powiązany z Bitbucket. Prawidłowy status nie gwarantuje braku problemów u każdego użytkownika, urządzenia lub regionu.
Jak Uptimus monitoruje Bitbucket
Otrzymuj alerty, gdy Bitbucket lub monitorowany komponent zgłasza poważną albo krytyczną awarię. Alerty mogą trafiać przez kanały włączone w workspace, w tym e-mail, push i skonfigurowane integracje. Dostępna historia zawiera 51 incydentów i zapewnia kontekst wykraczający poza bieżący status. Ostatni zarejestrowany incydent to „BitBucket Site fails to Load”.
Otrzymuj alerty o obniżonej wydajności, częściowym wpływie i mniejszych incydentach. Uptimus monitoruje obecnie 13 komponentów Bitbucket: Website, API, Git via SSH, Authentication and user management. Alerty mogą trafiać przez kanały włączone w workspace, w tym e-mail, push i skonfigurowane integracje.
