by HonkWatch

Is Netlify down in French Polynesia?

No problems reported with Netlify right now

French Polynesia No reports in the last hour checked just now
Netlify reports no current incident. Updated 6 Nov, 16:22 UTC, just now · Official status page
Report a problemFollow community reports
Change country

Reports from people in French Polynesia

Last 24 hours · French Polynesia · times in UTC

0 reports

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

024 18:0000:0006:0012:00

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

Report totals as of 6 Nov, 16:22 UTC

Report a problem with Netlify

Having trouble? Tap what isn't working. No account needed.

What isn't working?

Anonymous · one report per service per hour. This adds your experience to the chart, without contacting the provider or subscribing you to alerts.

Compare worldwide reports · Other services in French Polynesia

Monitor the provider status with HonkWatch

Get monitoring alerts for Netlify

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

Free account required. Netlify is selected on the next page. Review the monitor and choose where alerts go. Community reports do not trigger these monitoring alerts.

Start free Log in

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

Our own checks of netlify.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Dallas: loaded in 510 ms Tokyo: loaded in 3177 ms Tel Aviv: loaded in 507 ms Singapore: loaded in 218 ms Portsmouth: loaded in 188 ms Johannesburg: loaded in 213 ms São Paulo: loaded in 142 ms New Jersey: loaded in 1814 ms Santiago: loaded in 416 ms Delhi: loaded in 347 ms Madrid: loaded in 225 ms Los Angeles: loaded in 327 ms Melbourne: loaded in 298 ms Jakarta: loaded in 277 ms Toronto: loaded in 607 ms Hamina: loaded in 380 ms Seoul: loaded in 218 ms Atlanta: loaded in 205 ms Bangalore: loaded in 277 ms New York: loaded in 192 ms Lauterbourg: loaded in 1466 ms St. Louis: loaded in 641 ms Port Louis: loaded in 1006 ms Sydney: loaded in 395 ms Querétaro: loaded in 481 ms Warsaw: loaded in 224 ms Cape Town: loaded in 512 ms Seattle: loaded in 246 ms Amsterdam: loaded in 176 ms Osaka: loaded in 204 ms Hong Kong: loaded in 381 ms Doha: loaded in 775 ms Mumbai: loaded in 248 ms Frankfurt: loaded in 126 ms London: loaded in 213 ms
  • DallasReachable510 ms, just now
  • TokyoReachable3177 ms, just now
  • Tel AvivReachable507 ms, 1 min ago
  • SingaporeReachable218 ms, 2 min ago
  • PortsmouthReachable188 ms, 2 min ago
  • JohannesburgReachable213 ms, 2 min ago
  • São PauloReachable142 ms, 2 min ago
  • New JerseyReachable1814 ms, 2 min ago
  • SantiagoReachable416 ms, 2 min ago
  • DelhiReachable347 ms, 2 min ago
  • MadridReachable225 ms, 2 min ago
  • Los AngelesReachable327 ms, 2 min ago
  • MelbourneReachable298 ms, 2 min ago
  • JakartaReachable277 ms, 3 min ago
  • TorontoReachable607 ms, 3 min ago
  • HaminaReachable380 ms, 3 min ago
  • SeoulReachable218 ms, 3 min ago
  • AtlantaReachable205 ms, 3 min ago
  • BangaloreReachable277 ms, 3 min ago
  • New YorkReachable192 ms, 3 min ago
  • LauterbourgReachable1466 ms, 3 min ago
  • St. LouisReachable641 ms, 3 min ago
  • Port LouisReachable1006 ms, 3 min ago
  • SydneyReachable395 ms, 3 min ago
  • QuerétaroReachable481 ms, 3 min ago
  • WarsawReachable224 ms, 3 min ago
  • Cape TownReachable512 ms, 3 min ago
  • SeattleReachable246 ms, 4 min ago
  • AmsterdamReachable176 ms, 4 min ago
  • OsakaReachable204 ms, 4 min ago
  • Hong KongReachable381 ms, 6 min ago
  • DohaReachable775 ms, 6 min ago
  • MumbaiReachable248 ms, 7 min ago
  • FrankfurtReachable126 ms, 8 min ago
  • LondonReachable213 ms, 8 min ago

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

Parts of Netlify

Netlify
  • High-Performance Edge NetworkOperational
  • Standard Edge NetworkOperational
  • Origin ServersOperational
  • Build PipelineOperational
  • Netlify Application UIOperational
  • APIOperational
  • Hosted DNSOperational
  • PrerenderingOperational
  • IdentityOperational
  • Netlify FunctionsOperational
  • AnalyticsOperational
  • Log DrainsOperational
  • Collaborative Deploy PreviewsOperational
  • Git GatewayOperational
  • Edge FunctionsOperational
  • Netlify Image CDNOperational
  • Netlify BlobsOperational
  • Netlify ObservabilityOperational
  • Netlify ConnectOperational
  • Netlify Create APIOperational
  • Visual EditorOperational
  • Netlify FormsOperational
  • Netlify Support ForumsOperational
  • Netlify HelpdeskOperational
  • Domain PurchasingOperational
  • BillingOperational
  • Agent RunnersOperational
  • AI GatewayOperational
  • Live TunnelOperational
  • Netlify DatabaseOperational
  • Edge Function LogsOperational
  • Function LogsOperational

Third-Party Services

  • Atlassian Bitbucket APIOperational
  • Atlassian Bitbucket WebhooksOperational
  • Atlassian Bitbucket SSHOperational
  • npm, Inc. Registry ReadsOperational
  • GitHub API RequestsOperational
  • GitHub WebhooksOperational
  • GitHub Git OperationsOperational
  • NS1 APIOperational
  • NS1 Management PortalOperational
  • Name.comOperational

Incidents and maintenance

No open incidents or planned maintenance.

Outage history

Last problem: 4 Nov, 17:18 UTC, partial outage for 5 min (1 of 42 parts affected: Build Pipeline).

Last 9030 days

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

Of the last 90 days, 2 had a partial or major outage, 0 had maintenance only and 85 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 netlify.com that failed (9,614 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 0% of 102 checks failed0% of 111 checks failed0% of 103 checks failed0% of 107 checks failed0% of 105 checks failed0% of 104 checks failed0% of 100 checks failed0% of 92 checks failed0% of 108 checks failed0% of 100 checks failed0% of 100 checks failed0% of 103 checks failed0% of 91 checks failed0% of 102 checks failed0% of 96 checks failed0% of 96 checks failed0% of 113 checks failed0% of 104 checks failed0% of 105 checks failed0% of 103 checks failed0% of 104 checks failed0% of 105 checks failed0% of 107 checks failed0% of 102 checks failed0% of 108 checks failed0% of 102 checks failed0% of 104 checks failed0% of 103 checks failed0% of 108 checks failed0% of 107 checks failed0% of 105 checks failed0% of 104 checks failed0% of 106 checks failed0% of 105 checks failed0% of 105 checks failed0% of 104 checks failed0% of 106 checks failed0% of 105 checks failed0% of 104 checks failed0% of 107 checks failed0% of 105 checks failed0% of 104 checks failed0% of 105 checks failed0% of 102 checks failed0% of 106 checks failed0% of 106 checks failed0% of 107 checks failed0% of 104 checks failed0% of 106 checks failed0% of 104 checks failed0% of 105 checks failed0% of 105 checks failed0% of 104 checks failed0% of 106 checks failed0% of 104 checks failed0% of 107 checks failed0% of 104 checks failed0% of 104 checks failed0% of 106 checks failed0% of 105 checks failed0% of 102 checks failed0% of 104 checks failed0% of 108 checks failed0% of 106 checks failed0% of 106 checks failed0% of 104 checks failed0% of 104 checks failed0% of 101 checks failed0% of 103 checks failed0% of 98 checks failed0% of 95 checks failed0% of 100 checks failed0% of 105 checks failed0% of 102 checks failed0% of 79 checks failed0% of 83 checks failed0% of 101 checks failed0% of 95 checks failed0% of 105 checks failed0% of 98 checks failed0% of 96 checks failed0% of 83 checks failed0% of 87 checks failed0% of 95 checks failed0% of 94 checks failed0% of 91 checks failed0% of 84 checks failed0% of 100 checks failed0% of 82 checks failed0% of 95 checks failed0% of 88 checks failed0% of 70 checks failed0% of 89 checks failed0% of 82 checks failed0% of 82 checks failed0% of 52 checks failed

Recent problems

4 Nov, 17:18 UTCPartial outage5 min1 of 42 parts affected: Build Pipeline
4 Nov, 16:14 UTCPartial outage32 min1 of 42 parts affected: Third-Party Services / GitHub Webhooks
4 Nov, 10:04 UTCPartial outage1 h 28 min2 of 42 parts affected: Third-Party Services / GitHub API Requests, Third-Party Services / GitHub Git Operations
3 Nov, 21:08 UTCPartial outage1 h 36 min1 of 42 parts affected: Third-Party Services / GitHub Git Operations
What can I try?

Having trouble with Netlify?

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

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

More in Cloud and hosting

See the live outage feed for French Polynesia · Find another service