by HonkWatch

Is Jira down in Mozambique?

Jira problems reported by people in Mozambique. 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 Mozambique

Last 24 hours · Mozambique · times in UTC

0 reports

No community reports in the last 24 hours from Mozambique. 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 Mozambique

Provider updates and website checks — worldwide

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

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

Having trouble with Jira?

  1. Compare reports from Mozambique 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,923 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 2% of 106 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 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 36 checks failed

Our own checks of atlassian.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

St. Louis: loaded in 412 ms Johannesburg: loaded in 2033 ms London: loaded in 414 ms Sydney: loaded in 355 ms Toronto: loaded in 480 ms Portsmouth: loaded in 520 ms Delhi: loaded in 643 ms Tel Aviv: loaded in 630 ms Warsaw: loaded in 433 ms Santiago: loaded in 661 ms Osaka: loaded in 732 ms Frankfurt: loaded in 373 ms Querétaro: loaded in 513 ms Seattle: loaded in 485 ms Port Louis: loaded in 2296 ms Los Angeles: loaded in 691 ms Hamina: loaded in 825 ms Melbourne: loaded in 357 ms New Jersey: loaded in 1390 ms Singapore: loaded in 386 ms Jakarta: loaded in 449 ms Seoul: loaded in 1219 ms Madrid: loaded in 630 ms Bangalore: loaded in 605 ms Cape Town: loaded in 1006 ms Lauterbourg: loaded in 594 ms Doha: loaded in 736 ms Hong Kong: loaded in 498 ms Amsterdam: loaded in 330 ms Mumbai: loaded in 544 ms Atlanta: loaded in 504 ms Tokyo: loaded in 1508 ms Dallas: loaded in 474 ms New York: loaded in 543 ms São Paulo: loaded in 461 ms
  • St. LouisReachable412 ms, just now
  • JohannesburgReachable2033 ms, just now
  • LondonReachable414 ms, just now
  • SydneyReachable355 ms, just now
  • TorontoReachable480 ms, just now
  • PortsmouthReachable520 ms, just now
  • DelhiReachable643 ms, just now
  • Tel AvivReachable630 ms, 1 min ago
  • WarsawReachable433 ms, 4 min ago
  • SantiagoReachable661 ms, 4 min ago
  • OsakaReachable732 ms, 4 min ago
  • FrankfurtReachable373 ms, 4 min ago
  • QuerétaroReachable513 ms, 4 min ago
  • SeattleReachable485 ms, 4 min ago
  • Port LouisReachable2296 ms, 4 min ago
  • Los AngelesReachable691 ms, 5 min ago
  • HaminaReachable825 ms, 5 min ago
  • MelbourneReachable357 ms, 5 min ago
  • New JerseyReachable1390 ms, 5 min ago
  • SingaporeReachable386 ms, 5 min ago
  • JakartaReachable449 ms, 5 min ago
  • SeoulReachable1219 ms, 5 min ago
  • MadridReachable630 ms, 5 min ago
  • BangaloreReachable605 ms, 5 min ago
  • Cape TownReachable1006 ms, 5 min ago
  • LauterbourgReachable594 ms, 5 min ago
  • DohaReachable736 ms, 5 min ago
  • Hong KongReachable498 ms, 5 min ago
  • AmsterdamReachable330 ms, 5 min ago
  • MumbaiReachable544 ms, 5 min ago
  • AtlantaReachable504 ms, 5 min ago
  • TokyoReachable1508 ms, 5 min ago
  • DallasReachable474 ms, 8 min ago
  • New YorkReachable543 ms, 8 min ago
  • São PauloReachable461 ms, 8 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