by HonkWatch

Is Jira down in Equatorial Guinea?

Jira problems reported by people in Equatorial Guinea. Check the last 24 hours and tell others what isn't working for you.

Having trouble with Jira?

Tell others what's happening. No account needed.

What isn't working?

One report per service per hour. Reports are anonymous; your IP address is not stored in the report.

Reports from people in Equatorial Guinea

Last 24 hours · Equatorial Guinea · times in UTC

0 reports

No community reports in the last 24 hours from Equatorial Guinea. This does not prove the service is working. If you have a problem, report it here.

024 18:0000:0006:0012:00

Reports per 15 minutes. A flat chart means no reports, not proof that everything works.

Compare worldwide reports · Other services in Equatorial Guinea

Provider updates and website checks — worldwide

The evidence below covers the provider and our available checks. It is not a separate verdict for Equatorial Guinea. The report chart above is filtered to Equatorial Guinea.

No. Jira is working. Updated 5 Nov, 16:03 UTC, 1 min ago · Official status page No problems recorded since 2 Nov 2026.

Having trouble with Jira?

  1. Compare reports from Equatorial Guinea and check the latest update above. A quiet chart does not rule out a new or local problem.
  2. Try the service on another device or switch between WiFi and mobile data, if available. If other sites also fail, check your internet provider.
  3. Report a problem with the feature that is failing and the country where you are affected. Submit once; your report appears in the chart.

Reports describe people's experiences. One report alone does not confirm an outage.

Last 9030 days

100.00% of the time without a reported outage, since 2 Nov

Of the last 90 days, 0 had a partial or major outage, 0 had maintenance only and 86 have no data. Recent problems are listed in a table further down.

90 days ago30 days agoToday

No problems Partial outage Major outage Maintenance No data yet

Last 24 hours

Every 15 minutes, hours in UTC

Bars: the share of our own checks of atlassian.com that failed (9,884 checks). Its status page reported no problem in this time. Community reports appear separately above, alongside our checks and provider updates.

0%5%10% 18:0000:0006:0012:00 1% of 105 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed2% of 108 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed4% of 111 checks failed0% of 102 checks failed0% of 102 checks failed1% of 105 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed2% of 106 checks failed2% of 107 checks failed0% of 102 checks failed0% of 102 checks failed1% of 105 checks failed1% of 105 checks failed0% of 102 checks failed1% of 105 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed1% of 105 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed3% of 109 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed1% of 105 checks failed1% of 105 checks failed0% of 102 checks failed1% of 105 checks failed2% of 107 checks failed0% of 102 checks failed1% of 105 checks failed0% of 102 checks failed0% of 102 checks failed3% of 111 checks failed1% of 105 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 105 checks failed1% of 108 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed1% of 108 checks failed1% of 106 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed1% of 108 checks failed0% of 105 checks failed1% of 108 checks failed0% of 105 checks failed1% of 106 checks failed2% of 111 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed1% of 106 checks failed0% of 105 checks failed0% of 105 checks failed1% of 108 checks failed0% of 105 checks failed0% of 104 checks failed0% of 106 checks failed1% of 108 checks failed1% of 108 checks failed1% of 107 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 94 checks failed2% of 88 checks failed0% of 102 checks failed0% of 1 checks failed

Our own checks of atlassian.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Santiago: loaded in 853 ms Seattle: loaded in 423 ms Frankfurt: loaded in 363 ms Port Louis: loaded in 1842 ms Delhi: loaded in 567 ms Osaka: loaded in 675 ms Dallas: loaded in 540 ms Melbourne: loaded in 475 ms Los Angeles: loaded in 586 ms Bangalore: loaded in 724 ms Querétaro: loaded in 491 ms New Jersey: loaded in 374 ms Hamina: loaded in 546 ms Tokyo: loaded in 612 ms Mumbai: loaded in 472 ms Lauterbourg: loaded in 480 ms Doha: loaded in 696 ms Madrid: loaded in 524 ms Singapore: loaded in 370 ms Jakarta: loaded in 420 ms Hong Kong: loaded in 616 ms Seoul: loaded in 858 ms Warsaw: loaded in 441 ms Amsterdam: loaded in 353 ms Toronto: loaded in 581 ms Atlanta: loaded in 399 ms Johannesburg: loaded in 1862 ms New York: loaded in 371 ms Sydney: loaded in 360 ms Tel Aviv: loaded in 688 ms Portsmouth: loaded in 651 ms São Paulo: loaded in 513 ms St. Louis: loaded in 488 ms Cape Town: loaded in 1004 ms London: loaded in 483 ms
  • SantiagoReachable853 ms, 1 min ago
  • SeattleReachable423 ms, 1 min ago
  • FrankfurtReachable363 ms, 1 min ago
  • Port LouisReachable1842 ms, 1 min ago
  • DelhiReachable567 ms, 1 min ago
  • OsakaReachable675 ms, 2 min ago
  • DallasReachable540 ms, 2 min ago
  • MelbourneReachable475 ms, 2 min ago
  • Los AngelesReachable586 ms, 2 min ago
  • BangaloreReachable724 ms, 2 min ago
  • QuerétaroReachable491 ms, 2 min ago
  • New JerseyReachable374 ms, 2 min ago
  • HaminaReachable546 ms, 2 min ago
  • TokyoReachable612 ms, 2 min ago
  • MumbaiReachable472 ms, 2 min ago
  • LauterbourgReachable480 ms, 2 min ago
  • DohaReachable696 ms, 2 min ago
  • MadridReachable524 ms, 2 min ago
  • SingaporeReachable370 ms, 2 min ago
  • JakartaReachable420 ms, 2 min ago
  • Hong KongReachable616 ms, 2 min ago
  • SeoulReachable858 ms, 2 min ago
  • WarsawReachable441 ms, 2 min ago
  • AmsterdamReachable353 ms, 3 min ago
  • TorontoReachable581 ms, 3 min ago
  • AtlantaReachable399 ms, 3 min ago
  • JohannesburgReachable1862 ms, 3 min ago
  • New YorkReachable371 ms, 3 min ago
  • SydneyReachable360 ms, 3 min ago
  • Tel AvivReachable688 ms, 3 min ago
  • PortsmouthReachable651 ms, 3 min ago
  • São PauloReachable513 ms, 3 min ago
  • St. LouisReachable488 ms, 3 min ago
  • Cape TownReachable1004 ms, 3 min ago
  • LondonReachable483 ms, 3 min ago

This is separate from the status page: we request atlassian.com and note whether it answers. These automated checks do not sign in or use the app's features.

Parts of Jira

Jira
  • Viewing contentOperational
  • Create and editOperational
  • Authentication and User ManagementOperational
  • SearchOperational
  • NotificationsOperational
  • AdministrationOperational
  • MarketplaceOperational
  • MobileOperational
  • Purchasing & LicensingOperational
  • SignupOperational
  • Automation for JiraOperational
  • WebhooksOperational

Incidents and maintenance

No open incidents or planned maintenance.

Recent problems

No problems recorded since 2 Nov 2026.

Alert me when Jira is down

HonkWatch watches the Jira status page for you and alerts you by email, Slack, Discord or Telegram when it reports a problem.

Start free Log in

More in Productivity

Questions

Is Jira down, or is it just me?

The Jira status page reports no problem and our own checks reach atlassian.com. This does not rule out problems with sign-in, payments, an app or a local network. Check the community reports above and report your experience.

How do we know?

We read the official Jira status page and load atlassian.com from our own probes in several cities. People can also report problems here. Their reports appear separately and may reveal issues before a provider update.

How often do we check?

The status page every 2.5 minutes, day and night, and the website every 5 minutes. We keep 90 days of history: a day we have no reading for shows as "no data yet", never as working.

Official status from the Jira status page.

← All services