← HonkWatch.com

Is Boomi down in Afghanistan?

No problems reported with Boomi right now

People in Afghanistan: 0 reports in the last hour Official page: No incident reported, checked 9 min ago Our checks: loads from 35 of 35 places
Boomi reports no current incident. Updated 8 Nov, 09:03 UTC, 9 min ago · Official status page
Report a problem
Change country

Known issues (from Boomi's status page)

Maintenance

  • November Boomi Enterprise Platform Release (planned) 14 Nov, 08:00 UTC to 14 Nov, 12:00 UTC. Affects Platform UI and Public API · Details Latest update (2 Nov, 16:31 UTC): During this time, Boomi will be performing updates to platform.boomi.com as part of the Boomi Enterprise Platform Release cycle. The Boomi Enterprise Platform may be unavailable for brief periods during this maintenance window. If your Integration Runtime was not already updated during the Runtime R
  • November Runtime Release [Boomi Clouds] - US (planned) 14 Nov, 08:00 UTC to 14 Nov, 12:00 UTC. Affects ANZ Atom Cloud, USA East Hub Cloud 01, USA East Integration Cloud (Archived 02/2025), DEU Integration Cloud 01 and 27 more · Details Latest update (2 Nov, 16:50 UTC): During this time, all basic runtime and runtime cluster updates, whether Cloud-based or on-premises, will occur as part of the Boomi Enterprise Platform Release. All processes running on the basic runtime and the runtime cluster where the Runtime Release has been applied will be unaffected. Processe

In Boomi's own words, as we read them every 15 minutes, last 9 min ago. Read Boomi's status page

Reports from people in Afghanistan

Last 24 hours · Afghanistan · times in UTC

0 reports

No community reports in the last 24 hours from Afghanistan. Having trouble? Add your report.

Status page: maintenance, 7 Nov, 08:08 to 12:05 UTCStatus page: partial outage, 16:11 to 18:01 UTC 024 12:0018:0000:0006:00 09:15-09:20 UTC: 34 of 34 places loaded it, typical 56 ms09:20-09:25 UTC: 35 of 35 places loaded it, typical 63 ms09:25-09:30 UTC: 34 of 34 places loaded it, typical 63 ms09:30-09:40 UTC: 35 of 35 places loaded it, typical 58 to 73 ms09:40-09:45 UTC: 34 of 34 places loaded it, typical 39 ms09:45-09:55 UTC: 35 of 35 places loaded it, typical 51 to 70 ms09:55-10:00 UTC: 34 of 34 places loaded it, typical 50 ms10:00-10:10 UTC: 35 of 35 places loaded it, typical 56 to 61 ms10:10-10:15 UTC: 34 of 34 places loaded it, typical 68 ms10:15-10:20 UTC: 25 of 25 places loaded it, typical 56 ms10:20-10:25 UTC: 35 of 35 places loaded it, typical 73 ms10:25-10:30 UTC: 34 of 34 places loaded it, typical 62 ms10:30-10:40 UTC: 35 of 35 places loaded it, typical 43 to 51 ms10:40-10:45 UTC: 34 of 34 places loaded it, typical 61 ms10:45-10:55 UTC: 35 of 35 places loaded it, typical 48 to 73 ms10:55-11:00 UTC: 34 of 34 places loaded it, typical 43 ms11:00-11:10 UTC: 35 of 35 places loaded it, typical 45 to 48 ms11:10-11:15 UTC: 34 of 34 places loaded it, typical 65 ms11:15-11:20 UTC: 35 of 35 places loaded it, typical 57 ms11:20-11:30 UTC: 34 of 34 places loaded it, typical 46 to 52 ms11:30-11:35 UTC: 35 of 35 places loaded it, typical 46 ms11:35-11:40 UTC: 26 of 26 places loaded it, typical 51 ms11:40-11:50 UTC: 35 of 35 places loaded it, typical 34 to 54 ms11:50-12:00 UTC: 34 of 34 places loaded it, typical 51 to 62 ms12:00-12:05 UTC: 35 of 35 places loaded it, typical 72 ms12:05-12:15 UTC: 34 of 34 places loaded it, typical 51 to 68 ms12:15-12:25 UTC: 35 of 35 places loaded it, typical 50 to 59 ms12:25-12:30 UTC: 34 of 34 places loaded it, typical 59 ms12:30-12:40 UTC: 35 of 35 places loaded it, typical 48 to 56 ms12:40-12:45 UTC: 34 of 34 places loaded it, typical 53 ms12:45-12:55 UTC: 35 of 35 places loaded it, typical 48 to 74 ms12:55-13:00 UTC: 34 of 34 places loaded it, typical 62 ms13:00-13:10 UTC: 35 of 35 places loaded it, typical 59 to 74 ms13:10-13:15 UTC: 34 of 34 places loaded it, typical 58 ms13:15-13:20 UTC: 35 of 35 places loaded it, typical 64 ms13:20-13:30 UTC: 34 of 34 places loaded it, typical 49 to 70 ms13:30-13:40 UTC: 35 of 35 places loaded it, typical 64 to 91 ms13:40-13:45 UTC: 34 of 34 places loaded it, typical 66 ms13:45-13:55 UTC: 35 of 35 places loaded it, typical 64 to 66 ms13:55-14:00 UTC: 34 of 34 places loaded it, typical 63 ms14:00-14:05 UTC: 35 of 35 places loaded it, typical 55 ms14:05-14:15 UTC: 34 of 34 places loaded it, typical 76 to 89 ms14:15-14:25 UTC: 35 of 35 places loaded it, typical 51 to 53 ms14:25-14:30 UTC: 34 of 34 places loaded it, typical 95 ms14:30-14:40 UTC: 35 of 35 places loaded it, typical 60 to 63 ms14:40-14:45 UTC: 34 of 34 places loaded it, typical 53 ms14:45-14:55 UTC: 35 of 35 places loaded it, typical 45 to 56 ms14:55-15:05 UTC: 34 of 34 places loaded it, typical 62 to 70 ms15:05-15:10 UTC: 35 of 35 places loaded it, typical 43 ms15:10-15:15 UTC: 34 of 34 places loaded it, typical 54 ms15:15-15:25 UTC: 35 of 35 places loaded it, typical 64 to 79 ms15:25-15:30 UTC: 34 of 34 places loaded it, typical 57 ms15:30-15:40 UTC: 35 of 35 places loaded it, typical 56 to 67 ms15:40-15:45 UTC: 34 of 34 places loaded it, typical 66 ms15:45-15:55 UTC: 35 of 35 places loaded it, typical 61 to 81 ms15:55-16:00 UTC: 34 of 34 places loaded it, typical 88 ms16:00-16:10 UTC: 35 of 35 places loaded it, typical 58 ms16:10-16:15 UTC: 34 of 34 places loaded it, typical 76 ms16:15-16:25 UTC: 35 of 35 places loaded it, typical 55 to 68 ms16:25-16:30 UTC: 34 of 34 places loaded it, typical 66 ms16:30-16:40 UTC: 35 of 35 places loaded it, typical 60 to 68 ms16:40-16:45 UTC: 34 of 34 places loaded it, typical 64 ms16:45-16:55 UTC: 35 of 35 places loaded it, typical 49 to 60 ms16:55-17:00 UTC: 33 of 33 places loaded it, typical 66 ms17:00-17:10 UTC: 35 of 35 places loaded it, typical 60 to 66 ms17:10-17:15 UTC: 34 of 34 places loaded it, typical 78 ms17:15-17:25 UTC: 35 of 35 places loaded it, typical 55 to 60 ms17:25-17:30 UTC: 34 of 34 places loaded it, typical 73 ms17:30-17:40 UTC: 35 of 35 places loaded it, typical 68 to 69 ms17:40-17:45 UTC: 34 of 34 places loaded it, typical 73 ms17:45-17:55 UTC: 35 of 35 places loaded it, typical 58 to 69 ms17:55-18:00 UTC: 34 of 34 places loaded it, typical 69 ms18:00-18:10 UTC: 35 of 35 places loaded it, typical 62 to 63 ms18:10-18:15 UTC: 34 of 34 places loaded it, typical 47 ms18:15-18:20 UTC: 35 of 35 places loaded it, typical 66 ms18:20-18:30 UTC: 34 of 34 places loaded it, typical 67 to 69 ms18:30-18:40 UTC: 35 of 35 places loaded it, typical 59 to 63 ms18:40-18:45 UTC: 34 of 34 places loaded it, typical 60 ms18:45-18:50 UTC: 35 of 35 places loaded it, typical 68 ms18:50-19:00 UTC: 34 of 34 places loaded it, typical 45 to 54 ms19:00-19:10 UTC: 35 of 35 places loaded it, typical 62 to 69 ms19:10-19:15 UTC: 33 of 33 places loaded it, typical 79 ms19:15-19:25 UTC: 35 of 35 places loaded it, typical 59 to 66 ms19:25-19:30 UTC: 34 of 34 places loaded it, typical 56 ms19:30-19:40 UTC: 35 of 35 places loaded it, typical 45 to 50 ms19:40-19:45 UTC: 34 of 34 places loaded it, typical 72 ms19:45-19:55 UTC: 35 of 35 places loaded it, typical 47 to 53 ms19:55-20:00 UTC: 34 of 34 places loaded it, typical 51 ms20:00-20:10 UTC: 35 of 35 places loaded it, typical 60 to 67 ms20:10-20:15 UTC: 34 of 34 places loaded it, typical 49 ms20:15-20:25 UTC: 35 of 35 places loaded it, typical 73 to 76 ms20:25-20:30 UTC: 34 of 34 places loaded it, typical 69 ms20:30-20:40 UTC: 35 of 35 places loaded it, typical 56 to 79 ms20:40-20:45 UTC: 34 of 34 places loaded it, typical 63 ms20:45-20:55 UTC: 35 of 35 places loaded it, typical 54 to 55 ms20:55-21:00 UTC: 34 of 34 places loaded it, typical 58 ms21:00-21:10 UTC: 35 of 35 places loaded it, typical 56 to 72 ms21:10-21:15 UTC: 34 of 34 places loaded it, typical 76 ms21:15-21:25 UTC: 35 of 35 places loaded it, typical 67 to 78 ms21:25-21:30 UTC: 34 of 34 places loaded it, typical 63 ms21:30-21:40 UTC: 35 of 35 places loaded it, typical 57 to 65 ms21:40-21:45 UTC: 34 of 34 places loaded it, typical 53 ms21:45-21:55 UTC: 35 of 35 places loaded it, typical 52 to 63 ms21:55-22:00 UTC: 34 of 34 places loaded it, typical 49 ms22:00-22:05 UTC: 35 of 35 places loaded it, typical 55 ms22:05-22:15 UTC: 34 of 34 places loaded it, typical 45 to 62 ms22:15-22:25 UTC: 35 of 35 places loaded it, typical 50 to 63 ms22:25-22:30 UTC: 34 of 34 places loaded it, typical 76 ms22:30-22:40 UTC: 35 of 35 places loaded it, typical 71 to 74 ms22:40-22:45 UTC: 34 of 34 places loaded it, typical 70 ms22:45-22:55 UTC: 35 of 35 places loaded it, typical 67 to 68 ms22:55-23:00 UTC: 34 of 34 places loaded it, typical 52 ms23:00-23:10 UTC: 35 of 35 places loaded it, typical 61 to 69 ms23:10-23:15 UTC: 34 of 34 places loaded it, typical 71 ms23:15-23:25 UTC: 35 of 35 places loaded it, typical 42 to 74 ms23:25-23:30 UTC: 34 of 34 places loaded it, typical 58 ms23:30-23:40 UTC: 35 of 35 places loaded it, typical 46 to 73 ms23:40-23:45 UTC: 33 of 33 places loaded it, typical 45 ms23:45-23:55 UTC: 35 of 35 places loaded it, typical 49 to 90 ms23:55-00:00 UTC: 34 of 34 places loaded it, typical 52 ms00:00-00:10 UTC: 35 of 35 places loaded it, typical 69 to 71 ms00:10-00:15 UTC: 34 of 34 places loaded it, typical 52 ms00:15-00:25 UTC: 35 of 35 places loaded it, typical 55 to 69 ms00:25-00:30 UTC: 34 of 34 places loaded it, typical 49 ms00:30-00:40 UTC: 35 of 35 places loaded it, typical 58 to 60 ms00:40-00:45 UTC: 34 of 34 places loaded it, typical 66 ms00:45-00:55 UTC: 35 of 35 places loaded it, typical 57 to 67 ms00:55-01:00 UTC: 34 of 34 places loaded it, typical 47 ms01:00-01:10 UTC: 35 of 35 places loaded it, typical 71 to 74 ms01:10-01:15 UTC: 34 of 34 places loaded it, typical 52 ms01:15-01:25 UTC: 35 of 35 places loaded it, typical 75 to 78 ms01:25-01:30 UTC: 34 of 34 places loaded it, typical 70 ms01:30-01:40 UTC: 35 of 35 places loaded it, typical 62 to 69 ms01:40-01:45 UTC: 34 of 34 places loaded it, typical 65 ms01:45-01:55 UTC: 35 of 35 places loaded it, typical 43 to 71 ms01:55-02:00 UTC: 34 of 34 places loaded it, typical 46 ms02:00-02:10 UTC: 35 of 35 places loaded it, typical 64 to 68 ms02:10-02:15 UTC: 34 of 34 places loaded it, typical 65 ms02:15-02:25 UTC: 35 of 35 places loaded it, typical 45 to 75 ms02:25-02:35 UTC: 34 of 34 places loaded it, typical 62 to 75 ms02:35-02:40 UTC: 35 of 35 places loaded it, typical 100 ms02:40-02:45 UTC: 34 of 34 places loaded it, typical 73 ms02:45-02:55 UTC: 35 of 35 places loaded it, typical 47 to 75 ms02:55-03:00 UTC: 34 of 34 places loaded it, typical 62 ms03:00-03:10 UTC: 35 of 35 places loaded it, typical 44 to 73 ms03:10-03:15 UTC: 34 of 34 places loaded it, typical 73 ms03:15-03:25 UTC: 35 of 35 places loaded it, typical 73 to 74 ms03:25-03:30 UTC: 34 of 34 places loaded it, typical 64 ms03:30-03:40 UTC: 35 of 35 places loaded it, typical 52 to 63 ms03:40-03:45 UTC: 34 of 34 places loaded it, typical 69 ms03:45-03:55 UTC: 35 of 35 places loaded it, typical 50 to 64 ms03:55-04:00 UTC: 34 of 34 places loaded it, typical 81 ms04:00-04:10 UTC: 35 of 35 places loaded it, typical 56 to 65 ms04:10-04:15 UTC: 34 of 34 places loaded it, typical 49 ms04:15-04:25 UTC: 35 of 35 places loaded it, typical 70 to 73 ms04:25-04:30 UTC: 34 of 34 places loaded it, typical 46 ms04:30-04:40 UTC: 35 of 35 places loaded it, typical 65 to 73 ms04:40-04:45 UTC: 34 of 34 places loaded it, typical 63 ms04:45-04:55 UTC: 35 of 35 places loaded it, typical 46 to 49 ms04:55-05:00 UTC: 34 of 34 places loaded it, typical 64 ms05:00-05:10 UTC: 35 of 35 places loaded it, typical 68 to 71 ms05:10-05:15 UTC: 33 of 33 places loaded it, typical 51 ms05:15-05:25 UTC: 35 of 35 places loaded it, typical 42 to 67 ms05:25-05:30 UTC: 34 of 34 places loaded it, typical 51 ms05:30-05:40 UTC: 35 of 35 places loaded it, typical 42 to 68 ms05:40-05:45 UTC: 34 of 34 places loaded it, typical 47 ms05:45-05:55 UTC: 35 of 35 places loaded it, typical 60 to 69 ms05:55-06:00 UTC: 34 of 34 places loaded it, typical 79 ms06:00-06:10 UTC: 35 of 35 places loaded it, typical 52 to 63 ms06:10-06:15 UTC: 34 of 34 places loaded it, typical 63 ms06:15-06:25 UTC: 35 of 35 places loaded it, typical 62 to 64 ms06:25-06:30 UTC: 34 of 34 places loaded it, typical 100 ms06:30-06:40 UTC: 35 of 35 places loaded it, typical 56 to 72 ms06:40-06:45 UTC: 34 of 34 places loaded it, typical 74 ms06:45-06:55 UTC: 35 of 35 places loaded it, typical 55 to 78 ms06:55-07:00 UTC: 34 of 34 places loaded it, typical 64 ms07:00-07:10 UTC: 35 of 35 places loaded it, typical 41 to 74 ms07:10-07:15 UTC: 33 of 33 places loaded it, typical 72 ms07:15-07:25 UTC: 35 of 35 places loaded it, typical 38 to 52 ms07:25-07:30 UTC: 34 of 34 places loaded it, typical 56 ms07:30-07:40 UTC: 35 of 35 places loaded it, typical 46 to 64 ms07:40-07:45 UTC: 34 of 34 places loaded it, typical 72 ms07:45-07:55 UTC: 35 of 35 places loaded it, typical 45 to 59 ms07:55-08:00 UTC: 34 of 34 places loaded it, typical 69 ms08:00-08:10 UTC: 35 of 35 places loaded it, typical 71 to 74 ms08:10-08:15 UTC: 34 of 34 places loaded it, typical 62 ms08:15-08:25 UTC: 35 of 35 places loaded it, typical 47 to 66 ms08:25-08:30 UTC: 34 of 34 places loaded it, typical 74 ms08:30-08:40 UTC: 35 of 35 places loaded it, typical 47 to 70 ms08:40-08:45 UTC: 34 of 34 places loaded it, typical 56 ms08:45-08:55 UTC: 35 of 35 places loaded it, typical 61 to 69 ms08:55-09:00 UTC: 34 of 34 places loaded it, typical 53 ms09:00-09:10 UTC: 35 of 35 places loaded it, typical 63 to 74 ms09:10-09:15 UTC: 24 of 24 places loaded it, typical 52 ms Typical response time of the places that loaded it, at most 100 ms

Bars: reports every 15 minutes. Reports alone do not confirm an outage; a flat chart does not prove everything works.

Tinted columns: when Boomi's status page showed a partial outage, a major outage or maintenance, as we read it every 15 minutes; the times are when we saw it, not when the provider posted it. Strip under the bars: how many places loaded boomi.com in each 5 minutes, of those that checked, and the line under it their typical response time. Any answer from the website counts as loaded, even an error page. Website checks don't test sign-in, payments or every feature. Tinted columns and our checks are worldwide; the bars count reports from Afghanistan only.

Latest checks, 09:10-09:15 UTC: 24 of 24 places loaded it, typical 52 ms.

Report totals as of 8 Nov, 09:12 UTC

Report a problem with Boomi

Choose where you are, then tap what isn't working. Tapping a problem sends your report; no account needed.

What isn't working? Tap one to send

Anonymous · one report per service per hour from each network. This adds your experience to the chart; the provider is not contacted.

Compare worldwide reports · Other services in Afghanistan

Where this status comes from

Provider updates and website checks — Worldwide

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

Our own checks of boomi.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Amsterdam: loaded in 18 ms Warsaw: loaded in 90 ms Delhi: loaded in 18 ms Querétaro: loaded in 293 ms São Paulo: loaded in 19 ms Sydney: loaded in 51 ms Madrid: loaded in 86 ms Mumbai: loaded in 36 ms Atlanta: loaded in 15 ms Frankfurt: loaded in 17 ms Osaka: loaded in 29 ms New York: loaded in 220 ms St. Louis: loaded in 156 ms New Jersey: loaded in 119 ms Seoul: loaded in 53 ms Melbourne: loaded in 74 ms Jakarta: loaded in 78 ms London: loaded in 23 ms Tokyo: loaded in 70 ms Johannesburg: loaded in 24 ms Toronto: loaded in 22 ms Hong Kong: loaded in 278 ms Portsmouth: loaded in 44 ms Los Angeles: loaded in 88 ms Dallas: loaded in 121 ms Lauterbourg: loaded in 46 ms Doha: loaded in 393 ms Bangalore: loaded in 40 ms Hamina: loaded in 41 ms Seattle: loaded in 112 ms Port Louis: loaded in 380 ms Cape Town: loaded in 43 ms Tel Aviv: loaded in 370 ms Santiago: loaded in 63 ms Singapore: loaded in 724 ms
  • AmsterdamReachable18 ms, 1 min ago
  • WarsawReachable90 ms, 1 min ago
  • DelhiReachable18 ms, 1 min ago
  • QuerétaroReachable293 ms, 1 min ago
  • São PauloReachable19 ms, 1 min ago
  • SydneyReachable51 ms, 1 min ago
  • MadridReachable86 ms, 1 min ago
  • MumbaiReachable36 ms, 1 min ago
  • AtlantaReachable15 ms, 1 min ago
  • FrankfurtReachable17 ms, 2 min ago
  • OsakaReachable29 ms, 2 min ago
  • New YorkReachable220 ms, 2 min ago
  • St. LouisReachable156 ms, 2 min ago
  • New JerseyReachable119 ms, 2 min ago
  • SeoulReachable53 ms, 2 min ago
  • MelbourneReachable74 ms, 2 min ago
  • JakartaReachable78 ms, 2 min ago
  • LondonReachable23 ms, 2 min ago
  • TokyoReachable70 ms, 2 min ago
  • JohannesburgReachable24 ms, 2 min ago
  • TorontoReachable22 ms, 2 min ago
  • Hong KongReachable278 ms, 2 min ago
  • PortsmouthReachable44 ms, 2 min ago
  • Los AngelesReachable88 ms, 2 min ago
  • DallasReachable121 ms, 2 min ago
  • LauterbourgReachable46 ms, 2 min ago
  • DohaReachable393 ms, 3 min ago
  • BangaloreReachable40 ms, 3 min ago
  • HaminaReachable41 ms, 3 min ago
  • SeattleReachable112 ms, 3 min ago
  • Port LouisReachable380 ms, 3 min ago
  • Cape TownReachable43 ms, 3 min ago
  • Tel AvivReachable370 ms, 3 min ago
  • SantiagoReachable63 ms, 3 min ago
  • SingaporeReachable724 ms, 3 min ago

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

Parts of Boomi

Boomi

All 119 listed parts are working.

Incidents and maintenance

Maintenance

  • November Boomi Enterprise Platform Release (planned) 14 Nov, 08:00 UTC to 14 Nov, 12:00 UTC. Affects Platform UI and Public API · Details
  • November Runtime Release [Boomi Clouds] - US (planned) 14 Nov, 08:00 UTC to 14 Nov, 12:00 UTC. Affects ANZ Atom Cloud, USA East Hub Cloud 01, USA East Integration Cloud (Archived 02/2025), DEU Integration Cloud 01 and 27 more · Details
Outage history

Last problem: 7 Nov, 16:11 UTC, partial outage for 1 h 50 min (1 of 119 parts affected: Boomi Platform / Runtime UI Status).

Last 9030 days

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

Of the last 90 days, 1 had a partial or major outage, 1 had maintenance only and 83 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

Recent problems

7 Nov, 16:11 UTCPartial outage1 h 50 min1 of 119 parts affected: Boomi Platform / Runtime UI Status
What can I try?

Having trouble with Boomi?

  1. Compare reports from Afghanistan 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.

Questions about these results

Questions

Is Boomi down, or is it just me?

The Boomi status page reports no problem and our own checks reach boomi.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 Boomi status page and load boomi.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 15 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.

Other services in Developer tools

Each card shows that service's own status, not Boomi's. A problem listed here does not mean Boomi has one.

See the live outage feed for Afghanistan · Find another service