Skip to content

Outage tracker / Ubisoft Connect

Is Ubisoft Connect down?

I'm having a problem

Checks passingchecked 1 minute ago

Our checks of Ubisoft Connect pass from all 10 regions we check.

As of Oct 23, 2026, 7:05 AM UTC, RealUptime's checks of Ubisoft Connect passed in all 10 regions that returned a reading.

Front-door and live API checks

Our checks of Ubisoft Connect did not fail from two or more distant regions in the 62 days we have checked it (since Aug 22, 2026). This does not show Ubisoft Connect works for users.

Email me when our checks of Ubisoft Connect fail from two or more distant regions

One email when our checks of Ubisoft Connect fail from two or more distant regions, and one when they pass, after you confirm the address. No account, no card.

This is our own reading from outside. It is not Ubisoft Connect's official status.

our check readinglive · checked Oct 23, 2026, 7:05 AM UTC
US-East896 msChecks passing
US-West1032 msChecks passing
Europe985 msChecks passing
Asia-Pacific2025 msChecks passing
US-Central862 msChecks passing
Canada809 msChecks passing
UK603 msChecks passing
Southeast Asia2489 msChecks passing
Australia3258 msChecks passing
South America2351 msChecks passing
their status pagetheir claim, not our reading

Ubisoft Connect publishes no status feed we can read, so the only reading here is our check reading on the left.

Ubisoft Connect response time, by region

US-East
1.3sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 1.5s2026-09-25 UTC: p95 751ms2026-09-26 UTC: p95 897ms2026-09-27 UTC: p95 759ms2026-09-28 UTC: p95 807ms2026-09-29 UTC: p95 745ms2026-09-30 UTC: p95 676ms2026-10-01 UTC: p95 727ms2026-10-02 UTC: p95 718ms2026-10-03 UTC: p95 718ms2026-10-04 UTC: p95 681ms2026-10-05 UTC: p95 738ms2026-10-06 UTC: p95 795ms2026-10-07 UTC: p95 716ms2026-10-08 UTC: p95 776ms2026-10-09 UTC: p95 670ms2026-10-10 UTC: p95 709ms2026-10-11 UTC: p95 736ms2026-10-12 UTC: p95 723ms2026-10-13 UTC: p95 678ms2026-10-14 UTC: p95 563ms2026-10-15 UTC: p95 573ms2026-10-16 UTC: p95 790ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 1.3s
Sep 24Oct 8Oct 23
US-West
1.8sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 872ms2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 1.0s2026-09-27 UTC: p95 962ms2026-09-28 UTC: p95 905ms2026-09-29 UTC: p95 926ms2026-09-30 UTC: p95 981ms2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 984ms2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 964ms2026-10-07 UTC: p95 924ms2026-10-08 UTC: p95 964ms2026-10-09 UTC: p95 934ms2026-10-10 UTC: p95 917ms2026-10-11 UTC: p95 1.0s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 968ms2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 941ms2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.8s2026-10-22 UTC: p95 1.9s2026-10-23 UTC: p95 1.8s
Sep 24Oct 8Oct 23
Europe
1.2sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 890ms2026-09-25 UTC: p95 1.5s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.6s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 770ms2026-10-02 UTC: p95 686ms2026-10-03 UTC: p95 647ms2026-10-04 UTC: p95 686ms2026-10-05 UTC: p95 672ms2026-10-06 UTC: p95 678ms2026-10-07 UTC: p95 616ms2026-10-08 UTC: p95 658ms2026-10-09 UTC: p95 609ms2026-10-10 UTC: p95 613ms2026-10-11 UTC: p95 675ms2026-10-12 UTC: p95 611ms2026-10-13 UTC: p95 572ms2026-10-14 UTC: p95 569ms2026-10-15 UTC: p95 588ms2026-10-16 UTC: p95 599ms2026-10-17 UTC: p95 652ms2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.2s
Sep 24Oct 8Oct 23
Asia-Pacific
2.6sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 2.0s2026-09-25 UTC: p95 1.9s2026-09-26 UTC: p95 1.8s2026-09-27 UTC: p95 1.8s2026-09-28 UTC: p95 1.8s2026-09-29 UTC: p95 1.9s2026-09-30 UTC: p95 1.7s2026-10-01 UTC: p95 1.7s2026-10-02 UTC: p95 1.7s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.5s2026-10-06 UTC: p95 1.7s2026-10-07 UTC: p95 1.6s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.7s2026-10-10 UTC: p95 1.7s2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 1.6s2026-10-13 UTC: p95 1.7s2026-10-14 UTC: p95 1.7s2026-10-15 UTC: p95 1.7s2026-10-16 UTC: p95 1.7s2026-10-17 UTC: p95 2.3s2026-10-18 UTC: p95 2.4s2026-10-19 UTC: p95 2.4s2026-10-20 UTC: p95 2.4s2026-10-21 UTC: p95 2.7s2026-10-22 UTC: p95 2.7s2026-10-23 UTC: p95 2.6s
Sep 24Oct 8Oct 23
US-Central
1.0sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 1.5s2026-09-25 UTC: p95 918ms2026-09-26 UTC: p95 884ms2026-09-27 UTC: p95 830ms2026-09-28 UTC: p95 817ms2026-09-29 UTC: p95 885ms2026-09-30 UTC: p95 911ms2026-10-01 UTC: p95 761ms2026-10-02 UTC: p95 717ms2026-10-03 UTC: p95 607ms2026-10-04 UTC: p95 786ms2026-10-05 UTC: p95 738ms2026-10-06 UTC: p95 723ms2026-10-07 UTC: p95 756ms2026-10-08 UTC: p95 708ms2026-10-09 UTC: p95 823ms2026-10-10 UTC: p95 842ms2026-10-11 UTC: p95 800ms2026-10-12 UTC: p95 769ms2026-10-13 UTC: p95 890ms2026-10-14 UTC: p95 905ms2026-10-15 UTC: p95 862ms2026-10-16 UTC: p95 843ms2026-10-17 UTC: p95 850ms2026-10-18 UTC: p95 938ms2026-10-19 UTC: p95 750ms2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.0s
Sep 24Oct 8Oct 23
Canada
1.2sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 1.8s2026-09-25 UTC: p95 975ms2026-09-26 UTC: p95 1.0s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 940ms2026-09-29 UTC: p95 1.2s2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 875ms2026-10-02 UTC: p95 1.0s2026-10-03 UTC: p95 937ms2026-10-04 UTC: p95 949ms2026-10-05 UTC: p95 941ms2026-10-06 UTC: p95 1.1s2026-10-07 UTC: p95 883ms2026-10-08 UTC: p95 777ms2026-10-09 UTC: p95 928ms2026-10-10 UTC: p95 927ms2026-10-11 UTC: p95 769ms2026-10-12 UTC: p95 900ms2026-10-13 UTC: p95 927ms2026-10-14 UTC: p95 932ms2026-10-15 UTC: p95 866ms2026-10-16 UTC: p95 814ms2026-10-17 UTC: p95 960ms2026-10-18 UTC: p95 781ms2026-10-19 UTC: p95 845ms2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.2s
Sep 24Oct 8Oct 23
UK
940msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 791ms2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 790ms2026-10-02 UTC: p95 619ms2026-10-03 UTC: p95 655ms2026-10-04 UTC: p95 637ms2026-10-05 UTC: p95 699ms2026-10-06 UTC: p95 686ms2026-10-07 UTC: p95 718ms2026-10-08 UTC: p95 692ms2026-10-09 UTC: p95 702ms2026-10-10 UTC: p95 710ms2026-10-11 UTC: p95 625ms2026-10-12 UTC: p95 679ms2026-10-13 UTC: p95 656ms2026-10-14 UTC: p95 620ms2026-10-15 UTC: p95 785ms2026-10-16 UTC: p95 730ms2026-10-17 UTC: p95 941ms2026-10-18 UTC: p95 984ms2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 932ms2026-10-22 UTC: p95 998ms2026-10-23 UTC: p95 940ms
Sep 24Oct 8Oct 23
Southeast Asia
3.2sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 3.5s2026-09-25 UTC: p95 3.6s2026-09-26 UTC: p95 3.2s2026-09-27 UTC: p95 3.0s2026-09-28 UTC: p95 3.1s2026-09-29 UTC: p95 3.3s2026-09-30 UTC: p95 3.0s2026-10-01 UTC: p95 2.2s2026-10-02 UTC: p95 2.1s2026-10-03 UTC: p95 2.2s2026-10-04 UTC: p95 2.2s2026-10-05 UTC: p95 2.2s2026-10-06 UTC: p95 2.2s2026-10-07 UTC: p95 2.1s2026-10-08 UTC: p95 2.1s2026-10-09 UTC: p95 2.2s2026-10-10 UTC: p95 2.4s2026-10-11 UTC: p95 2.1s2026-10-12 UTC: p95 2.1s2026-10-13 UTC: p95 2.0s2026-10-14 UTC: p95 2.1s2026-10-15 UTC: p95 2.0s2026-10-16 UTC: p95 2.1s2026-10-17 UTC: p95 2.6s2026-10-18 UTC: p95 2.8s2026-10-19 UTC: p95 2.9s2026-10-20 UTC: p95 3.1s2026-10-21 UTC: p95 3.2s2026-10-22 UTC: p95 3.1s2026-10-23 UTC: p95 3.2s
Sep 24Oct 8Oct 23
Australia
3.7sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 3.4s2026-09-25 UTC: p95 3.4s2026-09-26 UTC: p95 3.5s2026-09-27 UTC: p95 3.1s2026-09-28 UTC: p95 2.9s2026-09-29 UTC: p95 3.0s2026-09-30 UTC: p95 3.1s2026-10-01 UTC: p95 2.2s2026-10-02 UTC: p95 2.3s2026-10-03 UTC: p95 2.2s2026-10-04 UTC: p95 2.2s2026-10-05 UTC: p95 2.1s2026-10-06 UTC: p95 2.1s2026-10-07 UTC: p95 2.1s2026-10-08 UTC: p95 2.1s2026-10-09 UTC: p95 2.4s2026-10-10 UTC: p95 2.2s2026-10-11 UTC: p95 2.0s2026-10-12 UTC: p95 2.1s2026-10-13 UTC: p95 2.1s2026-10-14 UTC: p95 2.0s2026-10-15 UTC: p95 2.1s2026-10-16 UTC: p95 2.1s2026-10-17 UTC: p95 2.2s2026-10-18 UTC: p95 3.9s2026-10-19 UTC: p95 3.7s2026-10-20 UTC: p95 3.6s2026-10-21 UTC: p95 3.6s2026-10-22 UTC: p95 3.6s2026-10-23 UTC: p95 3.7s
Sep 24Oct 8Oct 23
South America
3.2sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 2.4s2026-09-25 UTC: p95 2.5s2026-09-26 UTC: p95 2.8s2026-09-27 UTC: p95 2.4s2026-09-28 UTC: p95 2.6s2026-09-29 UTC: p95 2.3s2026-09-30 UTC: p95 2.1s2026-10-01 UTC: p95 1.6s2026-10-02 UTC: p95 1.6s2026-10-03 UTC: p95 1.8s2026-10-04 UTC: p95 1.8s2026-10-05 UTC: p95 1.7s2026-10-06 UTC: p95 1.6s2026-10-07 UTC: p95 1.7s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.7s2026-10-10 UTC: p95 1.6s2026-10-11 UTC: p95 1.7s2026-10-12 UTC: p95 1.6s2026-10-13 UTC: p95 1.7s2026-10-14 UTC: p95 1.5s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.6s2026-10-17 UTC: p95 3s2026-10-18 UTC: p95 3.6s2026-10-19 UTC: p95 3.7s2026-10-20 UTC: p95 3.8s2026-10-21 UTC: p95 3.3s2026-10-22 UTC: p95 3.4s2026-10-23 UTC: p95 3.2s
Sep 24Oct 8Oct 23

Check your own site while you wait on Ubisoft Connect

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Ubisoft Connect. It cannot diagnose Ubisoft Connect's own systems.

What we measured, function by function

Ubisoft Connect answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 896msstatus code: 400checked: Oct 23, 2026, 6:56 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Ubisoft Connect normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1032msstatus code: 400checked: Oct 23, 2026, 6:58 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Ubisoft Connect normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 862msstatus code: 400checked: Oct 23, 2026, 6:59 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Ubisoft Connect normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 809msstatus code: 400checked: Oct 23, 2026, 7:04 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Ubisoft Connect normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 2351msstatus code: 400checked: Oct 23, 2026, 6:53 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Ubisoft Connect normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 985msstatus code: 400checked: Oct 23, 2026, 7:00 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Ubisoft Connect normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 603msstatus code: 400checked: Oct 23, 2026, 7:01 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Ubisoft Connect normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 2025msstatus code: 400checked: Oct 23, 2026, 7:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Ubisoft Connect normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 2489msstatus code: 400checked: Oct 23, 2026, 7:03 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Ubisoft Connect normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 3258msstatus code: 400checked: Oct 23, 2026, 6:50 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Ubisoft Connect normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Ubisoft Connect, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We started counting reports for Ubisoft Connect on September 9, 2026.

Recent probe events

No probe events on record yet for Ubisoft Connect.

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Ubisoft Connect since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Ubisoft Connect covering any window you pick, with our check readings and Ubisoft Connect's own claim at the time, side by side.

Full check history for Ubisoft Connect: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Put this badge in your README

Ubisoft Connect uptime by RealUptime's checksLive, from this page's own readings.
[![Ubisoft Connect uptime by RealUptime's checks](https://realuptime.io/outages/ubisoft/badge.svg?days=30)](https://realuptime.io/outages/ubisoft)
<a href="https://realuptime.io/outages/ubisoft"><img src="https://realuptime.io/outages/ubisoft/badge.svg?days=30" alt="Ubisoft Connect uptime by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Ubisoft Connect down?", https://realuptime.io/outages/ubisoft. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

How our checks compare with Ubisoft Connect's stated SLA

At or above your target

Our checks of Ubisoft Connect failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, not from Ubisoft Connect's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

secondary
https://www.ubisoft.com/en-us/
primaryfunctional: live API
https://public-ubiservices.ubi.com/v3/profiles/sessions

What our check can and cannot see

A pass means the service's servers answered our request with the error they give a request that carries no account or valid input. It does not show that sign-in works or that any real request succeeds.

Host checked: public-ubiservices.ubi.com

RealUptime is not affiliated with Ubisoft Connect; the name identifies what we checked, and nothing here speaks for Ubisoft Connect's own team. We send a single web request to Ubisoft Connect from 10 regions on our own schedule and time the response. We do not see inside Ubisoft Connect's systems, do not use an account or real transaction, and are not the same signal Ubisoft Connect's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Ubisoft Connect is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.