← HonkWatch.com

Is Planview down in Comoros?

No problems reported with Planview right now

People in Comoros: 0 reports in the last hour Official page: No incident reported, checked 10 min ago Our checks: loads from 35 of 35 places
Planview reports no current incident. Updated 7 Nov, 20:10 UTC, 10 min ago · Official status page
Report a problem
Change country

Known issues (from Planview's status page)

Maintenance

  • PPM Pro - Maintenance (planned) 11 Nov, 13:00 UTC to 11 Nov, 17:00 UTC. Affects APAC - PPM Pro Australia Datacenter · Details
  • R&V - Release 2.53.0 (planned) 14 Nov, 00:30 UTC to 14 Nov, 04:00 UTC. Affects UK - Release & Verify Production · Details

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

Reports from people in Comoros

Last 24 hours · Comoros · times in UTC

0 reports

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

Status page: maintenance, 23:15 to 00:02 UTCStatus page: maintenance, 06:02 to 07:04 UTCStatus page: maintenance, 12:41 to 16:04 UTC 024 00:0006:0012:0018:00 20:30-20:50 UTC: 34 of 34 places loaded it, typical 150 to 173 ms20:50-21:00 UTC: 35 of 35 places loaded it, typical 163 to 177 ms21:00-21:05 UTC: 11 of 11 places loaded it, typical 134 ms21:05-21:10 UTC: 26 of 26 places loaded it, typical 175 ms21:10-21:15 UTC: 35 of 35 places loaded it, typical 153 ms21:15-21:20 UTC: 19 of 19 places loaded it, typical 142 ms21:20-21:25 UTC: 35 of 35 places loaded it, typical 185 ms21:25-21:30 UTC: 18 of 18 places loaded it, typical 152 ms21:30-21:35 UTC: 31 of 31 places loaded it, typical 172 ms21:35-21:40 UTC: 34 of 34 places loaded it, typical 179 ms21:40-21:45 UTC: 35 of 35 places loaded it, typical 176 ms21:45-21:50 UTC: 27 of 27 places loaded it, typical 204 ms21:50-21:55 UTC: 17 of 17 places loaded it, typical 190 ms21:55-22:00 UTC: 32 of 32 places loaded it, typical 157 ms22:00-22:05 UTC: 35 of 35 places loaded it, typical 169 ms22:05-22:10 UTC: 30 of 30 places loaded it, typical 202 ms22:10-22:20 UTC: 35 of 35 places loaded it, typical 136 to 163 ms22:20-22:25 UTC: 34 of 34 places loaded it, typical 174 ms22:25-22:30 UTC: 30 of 30 places loaded it, typical 130 ms22:30-22:35 UTC: 35 of 35 places loaded it, typical 175 ms22:35-22:40 UTC: 34 of 34 places loaded it, typical 222 ms22:40-22:50 UTC: 35 of 35 places loaded it, typical 168 to 170 ms22:50-22:55 UTC: 33 of 33 places loaded it, typical 175 ms22:55-23:05 UTC: 35 of 35 places loaded it, typical 158 to 207 ms23:05-23:10 UTC: 34 of 34 places loaded it, typical 176 ms23:10-23:15 UTC: 33 of 33 places loaded it, typical 113 ms23:15-23:25 UTC: 34 of 34 places loaded it, typical 156 to 163 ms23:25-23:35 UTC: 35 of 35 places loaded it, typical 130 to 166 ms23:35-23:45 UTC: 34 of 34 places loaded it, typical 135 to 150 ms23:45-23:50 UTC: 35 of 35 places loaded it, typical 121 ms23:50-23:55 UTC: 33 of 33 places loaded it, typical 166 ms23:55-00:05 UTC: 35 of 35 places loaded it, typical 142 to 159 ms00:05-00:10 UTC: 34 of 34 places loaded it, typical 166 ms00:10-00:20 UTC: 35 of 35 places loaded it, typical 167 to 171 ms00:20-00:25 UTC: 34 of 34 places loaded it, typical 140 ms00:25-00:30 UTC: 35 of 35 places loaded it, typical 139 ms00:30-00:40 UTC: 34 of 34 places loaded it, typical 128 to 144 ms00:40-00:50 UTC: 35 of 35 places loaded it, typical 149 to 151 ms00:50-00:55 UTC: 34 of 34 places loaded it, typical 173 ms00:55-01:00 UTC: 35 of 35 places loaded it, typical 169 ms01:00-01:10 UTC: 34 of 34 places loaded it, typical 149 to 160 ms01:10-01:20 UTC: 35 of 35 places loaded it, typical 138 to 170 ms01:20-01:25 UTC: 34 of 34 places loaded it, typical 125 ms01:25-01:35 UTC: 35 of 35 places loaded it, typical 150 to 163 ms01:35-01:40 UTC: 34 of 34 places loaded it, typical 185 ms01:40-01:50 UTC: 35 of 35 places loaded it, typical 160 to 166 ms01:50-02:00 UTC: 34 of 34 places loaded it, typical 144 to 148 ms02:00-02:05 UTC: 35 of 35 places loaded it, typical 116 ms02:05-02:10 UTC: 34 of 34 places loaded it, typical 171 ms02:10-02:20 UTC: 35 of 35 places loaded it, typical 160 to 177 ms02:20-02:25 UTC: 34 of 34 places loaded it, typical 159 ms02:25-02:35 UTC: 35 of 35 places loaded it, typical 127 to 197 ms02:35-02:40 UTC: 34 of 34 places loaded it, typical 153 ms02:40-02:50 UTC: 35 of 35 places loaded it, typical 127 to 133 ms02:50-03:00 UTC: 34 of 34 places loaded it, typical 164 to 189 ms03:00-03:05 UTC: 35 of 35 places loaded it, typical 132 ms03:05-03:10 UTC: 33 of 33 places loaded it, typical 202 ms03:10-03:20 UTC: 35 of 35 places loaded it, typical 146 to 170 ms03:20-03:25 UTC: 34 of 34 places loaded it, typical 131 ms03:25-03:35 UTC: 35 of 35 places loaded it, typical 144 to 160 ms03:35-03:40 UTC: 34 of 34 places loaded it, typical 150 ms03:40-03:50 UTC: 35 of 35 places loaded it, typical 161 to 184 ms03:50-03:55 UTC: 34 of 34 places loaded it, typical 167 ms03:55-04:05 UTC: 35 of 35 places loaded it, typical 139 to 171 ms04:05-04:10 UTC: 34 of 34 places loaded it, typical 177 ms04:10-04:20 UTC: 35 of 35 places loaded it, typical 137 to 162 ms04:20-04:25 UTC: 34 of 34 places loaded it, typical 173 ms04:25-04:30 UTC: 35 of 35 places loaded it, typical 202 ms04:30-04:40 UTC: 34 of 34 places loaded it, typical 172 to 173 ms04:40-04:50 UTC: 35 of 35 places loaded it, typical 130 to 174 ms04:50-04:55 UTC: 34 of 34 places loaded it, typical 179 ms04:55-05:05 UTC: 35 of 35 places loaded it, typical 170 ms05:05-05:10 UTC: 34 of 34 places loaded it, typical 147 ms05:10-05:15 UTC: 35 of 35 places loaded it, typical 166 ms05:15-05:25 UTC: 34 of 34 places loaded it, typical 138 to 224 ms05:25-05:35 UTC: 35 of 35 places loaded it, typical 155 to 157 ms05:35-05:40 UTC: 34 of 34 places loaded it, typical 157 ms05:40-05:50 UTC: 35 of 35 places loaded it, typical 143 to 165 ms05:50-05:55 UTC: 34 of 34 places loaded it, typical 153 ms05:55-06:05 UTC: 35 of 35 places loaded it, typical 142 ms06:05-06:10 UTC: 33 of 33 places loaded it, typical 113 ms06:10-06:20 UTC: 35 of 35 places loaded it, typical 122 to 210 ms06:20-06:30 UTC: 34 of 34 places loaded it, typical 168 to 176 ms06:30-06:35 UTC: 35 of 35 places loaded it, typical 125 ms06:35-06:40 UTC: 34 of 34 places loaded it, typical 187 ms06:40-06:50 UTC: 35 of 35 places loaded it, typical 122 to 131 ms06:50-06:55 UTC: 34 of 34 places loaded it, typical 176 ms06:55-07:05 UTC: 35 of 35 places loaded it, typical 166 to 172 ms07:05-07:10 UTC: 34 of 34 places loaded it, typical 188 ms07:10-07:20 UTC: 35 of 35 places loaded it, typical 130 to 165 ms07:20-07:25 UTC: 34 of 34 places loaded it, typical 142 ms07:25-07:35 UTC: 35 of 35 places loaded it, typical 164 to 172 ms07:35-07:40 UTC: 34 of 34 places loaded it, typical 140 ms07:40-07:50 UTC: 35 of 35 places loaded it, typical 131 to 140 ms07:50-07:55 UTC: 34 of 34 places loaded it, typical 181 ms07:55-08:05 UTC: 35 of 35 places loaded it, typical 134 to 142 ms08:05-08:10 UTC: 33 of 33 places loaded it, typical 176 ms08:10-08:20 UTC: 35 of 35 places loaded it, typical 125 to 131 ms08:20-08:25 UTC: 34 of 34 places loaded it, typical 168 ms08:25-08:35 UTC: 35 of 35 places loaded it, typical 122 to 158 ms08:35-08:40 UTC: 34 of 34 places loaded it, typical 141 ms08:40-08:50 UTC: 35 of 35 places loaded it, typical 137 to 146 ms08:50-08:55 UTC: 33 of 33 places loaded it, typical 130 ms08:55-09:05 UTC: 35 of 35 places loaded it, typical 168 to 175 ms09:05-09:10 UTC: 34 of 34 places loaded it, typical 161 ms09:10-09:15 UTC: 35 of 35 places loaded it, typical 166 ms09:15-09:25 UTC: 34 of 34 places loaded it, typical 145 to 171 ms09:25-09:35 UTC: 35 of 35 places loaded it, typical 130 to 158 ms09:35-09:40 UTC: 34 of 34 places loaded it, typical 148 ms09:40-09:50 UTC: 35 of 35 places loaded it, typical 162 to 198 ms09:50-09:55 UTC: 34 of 34 places loaded it, typical 173 ms09:55-10:05 UTC: 35 of 35 places loaded it, typical 162 to 167 ms10:05-10:10 UTC: 33 of 33 places loaded it, typical 159 ms10:10-10:15 UTC: 35 of 35 places loaded it, typical 151 ms10:15-10:20 UTC: 21 of 21 places loaded it, typical 268 ms10:20-10:35 UTC: 35 of 35 places loaded it, typical 165 to 172 ms10:35-10:40 UTC: 33 of 33 places loaded it, typical 161 ms10:40-10:50 UTC: 35 of 35 places loaded it, typical 131 to 167 ms10:50-10:55 UTC: 34 of 34 places loaded it, typical 186 ms10:55-11:05 UTC: 35 of 35 places loaded it, typical 151 to 174 ms11:05-11:10 UTC: 34 of 34 places loaded it, typical 173 ms11:10-11:20 UTC: 35 of 35 places loaded it, typical 132 to 168 ms11:20-11:25 UTC: 34 of 34 places loaded it, typical 159 ms11:25-11:30 UTC: 35 of 35 places loaded it, typical 170 ms11:30-11:35 UTC: 34 of 34 places loaded it, typical 148 ms11:35-11:40 UTC: 18 of 18 places loaded it, typical 204 ms11:40-11:50 UTC: 35 of 35 places loaded it, typical 159 to 166 ms11:50-11:55 UTC: 34 of 34 places loaded it, typical 141 ms11:55-12:05 UTC: 35 of 35 places loaded it, typical 158 to 170 ms12:05-12:10 UTC: 34 of 34 places loaded it, typical 179 ms12:10-12:15 UTC: 35 of 35 places loaded it, typical 128 ms12:15-12:20 UTC: 33 of 33 places loaded it, typical 168 ms12:20-12:25 UTC: 34 of 34 places loaded it, typical 186 ms12:25-12:35 UTC: 35 of 35 places loaded it, typical 175 to 199 ms12:35-12:40 UTC: 34 of 34 places loaded it, typical 180 ms12:40-12:45 UTC: 35 of 35 places loaded it, typical 179 ms12:45-12:50 UTC: 34 of 34 places loaded it, typical 184 ms12:50-12:55 UTC: 32 of 32 places loaded it, typical 155 ms12:55-13:05 UTC: 35 of 35 places loaded it, typical 162 to 179 ms13:05-13:10 UTC: 34 of 34 places loaded it, typical 185 ms13:10-13:15 UTC: 33 of 33 places loaded it, typical 168 ms13:15-13:20 UTC: 35 of 35 places loaded it, typical 138 ms13:20-13:25 UTC: 34 of 34 places loaded it, typical 178 ms13:25-13:35 UTC: 35 of 35 places loaded it, typical 168 to 176 ms13:35-13:40 UTC: 34 of 34 places loaded it, typical 147 ms13:40-13:45 UTC: 35 of 35 places loaded it, typical 132 ms13:45-13:55 UTC: 34 of 34 places loaded it, typical 163 to 191 ms13:55-14:05 UTC: 35 of 35 places loaded it, typical 172 to 203 ms14:05-14:10 UTC: 34 of 34 places loaded it, typical 151 ms14:10-14:20 UTC: 35 of 35 places loaded it, typical 130 to 176 ms14:20-14:30 UTC: 34 of 34 places loaded it, typical 154 ms14:30-14:35 UTC: 35 of 35 places loaded it, typical 166 ms14:35-14:40 UTC: 34 of 34 places loaded it, typical 192 ms14:40-14:50 UTC: 35 of 35 places loaded it, typical 146 to 204 ms14:50-14:55 UTC: 34 of 34 places loaded it, typical 183 ms14:55-15:05 UTC: 35 of 35 places loaded it, typical 172 to 191 ms15:05-15:10 UTC: 34 of 34 places loaded it, typical 215 ms15:10-15:20 UTC: 35 of 35 places loaded it, typical 160 to 200 ms15:20-15:25 UTC: 34 of 34 places loaded it, typical 202 ms15:25-15:35 UTC: 35 of 35 places loaded it, typical 187 to 201 ms15:35-15:40 UTC: 34 of 34 places loaded it, typical 157 ms15:40-15:50 UTC: 35 of 35 places loaded it, typical 160 to 208 ms15:50-15:55 UTC: 34 of 34 places loaded it, typical 182 ms15:55-16:00 UTC: 35 of 35 places loaded it, typical 149 ms16:00-16:10 UTC: 34 of 34 places loaded it, typical 189 to 245 ms16:10-16:20 UTC: 35 of 35 places loaded it, typical 170 to 182 ms16:20-16:25 UTC: 34 of 34 places loaded it, typical 173 ms16:25-16:35 UTC: 35 of 35 places loaded it, typical 189 to 230 ms16:35-16:40 UTC: 34 of 34 places loaded it, typical 179 ms16:40-16:50 UTC: 35 of 35 places loaded it, typical 183 to 196 ms16:50-16:55 UTC: 33 of 33 places loaded it, typical 164 ms16:55-17:05 UTC: 35 of 35 places loaded it, typical 174 to 180 ms17:05-17:10 UTC: 34 of 34 places loaded it, typical 209 ms17:10-17:20 UTC: 35 of 35 places loaded it, typical 212 to 219 ms17:20-17:25 UTC: 34 of 34 places loaded it, typical 202 ms17:25-17:30 UTC: 35 of 35 places loaded it, typical 168 ms17:30-17:40 UTC: 34 of 34 places loaded it, typical 155 to 178 ms17:40-17:50 UTC: 35 of 35 places loaded it, typical 167 to 176 ms17:50-17:55 UTC: 34 of 34 places loaded it, typical 203 ms17:55-18:05 UTC: 35 of 35 places loaded it, typical 169 to 189 ms18:05-18:10 UTC: 34 of 34 places loaded it, typical 206 ms18:10-18:20 UTC: 35 of 35 places loaded it, typical 197 to 226 ms18:20-18:25 UTC: 33 of 33 places loaded it, typical 181 ms18:25-18:35 UTC: 35 of 35 places loaded it, typical 171 to 191 ms18:35-18:40 UTC: 34 of 34 places loaded it, typical 228 ms18:40-18:50 UTC: 35 of 35 places loaded it, typical 169 to 194 ms18:50-18:55 UTC: 34 of 34 places loaded it, typical 195 ms18:55-19:05 UTC: 35 of 35 places loaded it, typical 140 to 193 ms19:05-19:10 UTC: 34 of 34 places loaded it, typical 124 ms19:10-19:20 UTC: 35 of 35 places loaded it, typical 180 to 184 ms19:20-19:25 UTC: 34 of 34 places loaded it, typical 197 ms19:25-19:35 UTC: 35 of 35 places loaded it, typical 175 to 181 ms19:35-19:40 UTC: 34 of 34 places loaded it, typical 177 ms19:40-19:45 UTC: 35 of 35 places loaded it, typical 134 ms19:45-20:00 UTC: 34 of 34 places loaded it, typical 119 to 202 ms20:00-20:05 UTC: 35 of 35 places loaded it, typical 157 ms20:05-20:10 UTC: 34 of 34 places loaded it, typical 185 ms20:10-20:15 UTC: 35 of 35 places loaded it, typical 186 ms20:15-20:20 UTC: 33 of 33 places loaded it, typical 170 ms Typical response time of the places that loaded it, at most 268 ms

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

Tinted columns: when Planview'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 planview.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 Comoros only.

Latest checks, 20:15-20:20 UTC: 33 of 33 places loaded it, typical 170 ms.

Report totals as of 7 Nov, 20:19 UTC

Report a problem with Planview

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. This adds your experience to the chart; the provider is not contacted.

Compare worldwide reports · Other services in Comoros

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 Comoros. The report chart above is filtered to Comoros.

Our own checks of planview.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Hong Kong: loaded in 67 ms Bangalore: loaded in 543 ms Tokyo: loaded in 92 ms Portsmouth: loaded in 111 ms Mumbai: loaded in 528 ms Sydney: loaded in 84 ms Madrid: loaded in 268 ms Delhi: loaded in 62 ms Cape Town: loaded in 170 ms Atlanta: loaded in 171 ms Johannesburg: loaded in 72 ms Seoul: loaded in 189 ms São Paulo: loaded in 74 ms Frankfurt: loaded in 296 ms Santiago: loaded in 535 ms Toronto: loaded in 78 ms Osaka: loaded in 361 ms Amsterdam: loaded in 342 ms Dallas: loaded in 349 ms New York: loaded in 257 ms Querétaro: loaded in 343 ms St. Louis: loaded in 182 ms London: loaded in 397 ms Tel Aviv: loaded in 75 ms Los Angeles: loaded in 127 ms Warsaw: loaded in 364 ms New Jersey: loaded in 102 ms Doha: loaded in 446 ms Hamina: loaded in 94 ms Seattle: loaded in 97 ms Jakarta: loaded in 64 ms Singapore: loaded in 78 ms Melbourne: loaded in 122 ms Port Louis: loaded in 267 ms Lauterbourg: loaded in 80 ms
  • Hong KongReachable67 ms, just now
  • BangaloreReachable543 ms, just now
  • TokyoReachable92 ms, just now
  • PortsmouthReachable111 ms, just now
  • MumbaiReachable528 ms, just now
  • SydneyReachable84 ms, just now
  • MadridReachable268 ms, just now
  • DelhiReachable62 ms, just now
  • Cape TownReachable170 ms, just now
  • AtlantaReachable171 ms, just now
  • JohannesburgReachable72 ms, just now
  • SeoulReachable189 ms, just now
  • São PauloReachable74 ms, just now
  • FrankfurtReachable296 ms, just now
  • SantiagoReachable535 ms, 1 min ago
  • TorontoReachable78 ms, 1 min ago
  • OsakaReachable361 ms, 1 min ago
  • AmsterdamReachable342 ms, 1 min ago
  • DallasReachable349 ms, 1 min ago
  • New YorkReachable257 ms, 1 min ago
  • QuerétaroReachable343 ms, 1 min ago
  • St. LouisReachable182 ms, 1 min ago
  • LondonReachable397 ms, 1 min ago
  • Tel AvivReachable75 ms, 2 min ago
  • Los AngelesReachable127 ms, 2 min ago
  • WarsawReachable364 ms, 2 min ago
  • New JerseyReachable102 ms, 2 min ago
  • DohaReachable446 ms, 2 min ago
  • HaminaReachable94 ms, 2 min ago
  • SeattleReachable97 ms, 2 min ago
  • JakartaReachable64 ms, 5 min ago
  • SingaporeReachable78 ms, 5 min ago
  • MelbourneReachable122 ms, 5 min ago
  • Port LouisReachable267 ms, 5 min ago
  • LauterbourgReachable80 ms, 6 min ago

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

Parts of Planview

All 114 listed parts are working.

Incidents and maintenance

Maintenance

  • PPM Pro - Maintenance (planned) 11 Nov, 13:00 UTC to 11 Nov, 17:00 UTC. Affects APAC - PPM Pro Australia Datacenter · Details
  • R&V - Release 2.53.0 (planned) 14 Nov, 00:30 UTC to 14 Nov, 04:00 UTC. Affects UK - Release & Verify Production · Details
Outage history

No problems recorded since 2 Nov 2026.

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, 2 had maintenance only and 84 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

No problems recorded since 2 Nov 2026.

What can I try?

Having trouble with Planview?

  1. Compare reports from Comoros 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 Planview down, or is it just me?

The Planview status page reports no problem and our own checks reach planview.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 Planview status page and load planview.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 Productivity

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

See the live outage feed for Comoros · Find another service