Skip to content

Outage tracker / Adobe Creative Cloud

Is Adobe Creative Cloud down?

I'm having a problem

Checks passingchecked 2 minutes ago

Our checks of Adobe Creative Cloud pass from all 10 regions we check.

As of Oct 19, 2026, 9:27 PM UTC, RealUptime's checks of Adobe Creative Cloud passed in all 10 regions that returned a reading.

Front-door and live API checks

Our checks of Adobe Creative Cloud did not fail from two or more distant regions in the 60 days we have checked it (since Aug 20, 2026). This does not show Adobe Creative Cloud works for users.

our check readinglive · checked Oct 19, 2026, 9:27 PM UTC
US-East672 msChecks passing
US-West936 msChecks passing
Europe121 msChecks passing
Asia-Pacific1578 msChecks passing
US-Central389 msChecks passing
Canada653 msChecks passing
UK161 msChecks passing
Southeast Asia1391 msChecks passing
Australia939 msChecks passing
South America1927 msChecks passing
their status pagetheir claim, not our reading

Adobe Creative Cloud publishes no status feed we can read, so the only reading here is our check reading on the left.

Adobe Creative Cloud response time, by region

US-East
877msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 504ms2026-09-21 UTC: p95 456ms2026-09-22 UTC: p95 448ms2026-09-23 UTC: p95 524ms2026-09-24 UTC: p95 647ms2026-09-25 UTC: p95 534ms2026-09-26 UTC: p95 508ms2026-09-27 UTC: p95 522ms2026-09-28 UTC: p95 396ms2026-09-29 UTC: p95 518ms2026-09-30 UTC: p95 537ms2026-10-01 UTC: p95 552ms2026-10-02 UTC: p95 514ms2026-10-03 UTC: p95 566ms2026-10-04 UTC: p95 457ms2026-10-05 UTC: p95 321ms2026-10-06 UTC: p95 563ms2026-10-07 UTC: p95 416ms2026-10-08 UTC: p95 445ms2026-10-09 UTC: p95 555ms2026-10-10 UTC: p95 506ms2026-10-11 UTC: p95 479ms2026-10-12 UTC: p95 527ms2026-10-13 UTC: p95 530ms2026-10-14 UTC: p95 389ms2026-10-15 UTC: p95 584ms2026-10-16 UTC: p95 430ms2026-10-17 UTC: p95 747ms2026-10-18 UTC: p95 952ms2026-10-19 UTC: p95 877ms
Sep 20Oct 4Oct 19
US-West
1.2sp95 · 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-20 UTC: p95 388ms2026-09-21 UTC: p95 560ms2026-09-22 UTC: p95 600ms2026-09-23 UTC: p95 547ms2026-09-24 UTC: p95 395ms2026-09-25 UTC: p95 528ms2026-09-26 UTC: p95 498ms2026-09-27 UTC: p95 450ms2026-09-28 UTC: p95 406ms2026-09-29 UTC: p95 426ms2026-09-30 UTC: p95 600ms2026-10-01 UTC: p95 388ms2026-10-02 UTC: p95 328ms2026-10-03 UTC: p95 345ms2026-10-04 UTC: p95 424ms2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 343ms2026-10-07 UTC: p95 418ms2026-10-08 UTC: p95 423ms2026-10-09 UTC: p95 445ms2026-10-10 UTC: p95 442ms2026-10-11 UTC: p95 523ms2026-10-12 UTC: p95 481ms2026-10-13 UTC: p95 479ms2026-10-14 UTC: p95 528ms2026-10-15 UTC: p95 486ms2026-10-16 UTC: p95 464ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.2s
Sep 20Oct 4Oct 19
Europe
596msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 312ms2026-09-21 UTC: p95 338ms2026-09-22 UTC: p95 378ms2026-09-23 UTC: p95 306ms2026-09-24 UTC: p95 327ms2026-09-25 UTC: p95 329ms2026-09-26 UTC: p95 407ms2026-09-27 UTC: p95 341ms2026-09-28 UTC: p95 367ms2026-09-29 UTC: p95 515ms2026-09-30 UTC: p95 421ms2026-10-01 UTC: p95 406ms2026-10-02 UTC: p95 406ms2026-10-03 UTC: p95 377ms2026-10-04 UTC: p95 349ms2026-10-05 UTC: p95 335ms2026-10-06 UTC: p95 328ms2026-10-07 UTC: p95 348ms2026-10-08 UTC: p95 306ms2026-10-09 UTC: p95 288ms2026-10-10 UTC: p95 288ms2026-10-11 UTC: p95 307ms2026-10-12 UTC: p95 280ms2026-10-13 UTC: p95 312ms2026-10-14 UTC: p95 304ms2026-10-15 UTC: p95 264ms2026-10-16 UTC: p95 272ms2026-10-17 UTC: p95 309ms2026-10-18 UTC: p95 476ms2026-10-19 UTC: p95 596ms
Sep 20Oct 4Oct 19
Asia-Pacific
1.5sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 930ms2026-09-21 UTC: p95 775ms2026-09-22 UTC: p95 746ms2026-09-23 UTC: p95 805ms2026-09-24 UTC: p95 717ms2026-09-25 UTC: p95 762ms2026-09-26 UTC: p95 826ms2026-09-27 UTC: p95 714ms2026-09-28 UTC: p95 653ms2026-09-29 UTC: p95 726ms2026-09-30 UTC: p95 707ms2026-10-01 UTC: p95 824ms2026-10-02 UTC: p95 793ms2026-10-03 UTC: p95 645ms2026-10-04 UTC: p95 654ms2026-10-05 UTC: p95 703ms2026-10-06 UTC: p95 854ms2026-10-07 UTC: p95 560ms2026-10-08 UTC: p95 754ms2026-10-09 UTC: p95 711ms2026-10-10 UTC: p95 802ms2026-10-11 UTC: p95 771ms2026-10-12 UTC: p95 755ms2026-10-13 UTC: p95 718ms2026-10-14 UTC: p95 584ms2026-10-15 UTC: p95 711ms2026-10-16 UTC: p95 692ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.5s
Sep 20Oct 4Oct 19
US-Central
658msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 660ms2026-09-21 UTC: p95 516ms2026-09-22 UTC: p95 574ms2026-09-23 UTC: p95 739ms2026-09-24 UTC: p95 563ms2026-09-25 UTC: p95 557ms2026-09-26 UTC: p95 643ms2026-09-27 UTC: p95 565ms2026-09-28 UTC: p95 636ms2026-09-29 UTC: p95 664ms2026-09-30 UTC: p95 946ms2026-10-01 UTC: p95 645ms2026-10-02 UTC: p95 437ms2026-10-03 UTC: p95 730ms2026-10-04 UTC: p95 586ms2026-10-05 UTC: p95 464ms2026-10-06 UTC: p95 583ms2026-10-07 UTC: p95 586ms2026-10-08 UTC: p95 632ms2026-10-09 UTC: p95 560ms2026-10-10 UTC: p95 586ms2026-10-11 UTC: p95 494ms2026-10-12 UTC: p95 625ms2026-10-13 UTC: p95 484ms2026-10-14 UTC: p95 592ms2026-10-15 UTC: p95 565ms2026-10-16 UTC: p95 661ms2026-10-17 UTC: p95 628ms2026-10-18 UTC: p95 579ms2026-10-19 UTC: p95 658ms
Sep 20Oct 4Oct 19
Canada
647msp95 · 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-20 UTC: p95 496ms2026-09-21 UTC: p95 552ms2026-09-22 UTC: p95 663ms2026-09-23 UTC: p95 666ms2026-09-24 UTC: p95 677ms2026-09-25 UTC: p95 760ms2026-09-26 UTC: p95 723ms2026-09-27 UTC: p95 557ms2026-09-28 UTC: p95 697ms2026-09-29 UTC: p95 682ms2026-09-30 UTC: p95 703ms2026-10-01 UTC: p95 690ms2026-10-02 UTC: p95 786ms2026-10-03 UTC: p95 652ms2026-10-04 UTC: p95 610ms2026-10-05 UTC: p95 968ms2026-10-06 UTC: p95 1.2s2026-10-07 UTC: p95 636ms2026-10-08 UTC: p95 658ms2026-10-09 UTC: p95 730ms2026-10-10 UTC: p95 602ms2026-10-11 UTC: p95 586ms2026-10-12 UTC: p95 626ms2026-10-13 UTC: p95 687ms2026-10-14 UTC: p95 620ms2026-10-15 UTC: p95 566ms2026-10-16 UTC: p95 717ms2026-10-17 UTC: p95 708ms2026-10-18 UTC: p95 809ms2026-10-19 UTC: p95 647ms
Sep 20Oct 4Oct 19
UK
386msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 318ms2026-09-21 UTC: p95 390ms2026-09-22 UTC: p95 411ms2026-09-23 UTC: p95 385ms2026-09-24 UTC: p95 396ms2026-09-25 UTC: p95 400ms2026-09-26 UTC: p95 519ms2026-09-27 UTC: p95 478ms2026-09-28 UTC: p95 508ms2026-09-29 UTC: p95 513ms2026-09-30 UTC: p95 436ms2026-10-01 UTC: p95 401ms2026-10-02 UTC: p95 619ms2026-10-03 UTC: p95 610ms2026-10-04 UTC: p95 529ms2026-10-05 UTC: p95 383ms2026-10-06 UTC: p95 418ms2026-10-07 UTC: p95 430ms2026-10-08 UTC: p95 523ms2026-10-09 UTC: p95 392ms2026-10-10 UTC: p95 427ms2026-10-11 UTC: p95 406ms2026-10-12 UTC: p95 508ms2026-10-13 UTC: p95 294ms2026-10-14 UTC: p95 299ms2026-10-15 UTC: p95 296ms2026-10-16 UTC: p95 302ms2026-10-17 UTC: p95 481ms2026-10-18 UTC: p95 423ms2026-10-19 UTC: p95 386ms
Sep 20Oct 4Oct 19
Southeast Asia
2.5sp95 · 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-20 UTC: p95 1.4s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.8s2026-09-23 UTC: p95 1.8s2026-09-24 UTC: p95 1.5s2026-09-25 UTC: p95 1.7s2026-09-26 UTC: p95 1.9s2026-09-27 UTC: p95 2.2s2026-09-28 UTC: p95 1.8s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.0s2026-10-03 UTC: p95 822ms2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 1.1s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 986ms2026-10-15 UTC: p95 974ms2026-10-16 UTC: p95 880ms2026-10-17 UTC: p95 2.4s2026-10-18 UTC: p95 2.5s2026-10-19 UTC: p95 2.5s
Sep 20Oct 4Oct 19
Australia
1.3sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 953ms2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.5s2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 884ms2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 837ms2026-10-10 UTC: p95 862ms2026-10-11 UTC: p95 862ms2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 1.4s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.3s
Sep 20Oct 4Oct 19
South America
2.4sp95 · 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-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 923ms2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.7s2026-10-04 UTC: p95 1.7s2026-10-05 UTC: p95 877ms2026-10-06 UTC: p95 919ms2026-10-07 UTC: p95 2.2s2026-10-08 UTC: p95 1.7s2026-10-09 UTC: p95 1.6s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.0s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 786ms2026-10-16 UTC: p95 787ms2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.5s2026-10-19 UTC: p95 2.4s
Sep 20Oct 4Oct 19

Check your own site while you wait on Adobe Creative Cloud

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 Adobe Creative Cloud. It cannot diagnose Adobe Creative Cloud's own systems.

What we measured, function by function

Adobe Creative Cloud 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 auth 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
  • AuthprimaryUS-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

Get an email when our checks of Adobe Creative Cloud fail from two or more distant regions, and again when they pass

Get an email when our checks change

We will email you when our checks of Adobe Creative Cloud fail from two or more distant regions, and again when they pass. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when our checks fail from two or more distant regions, one when they pass, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is our own reading from outside. It is not Adobe Creative Cloud's official status.

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: 672msstatus code: 401checked: Oct 19, 2026, 9:22 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Adobe Creative Cloud normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 936msstatus code: 401checked: Oct 19, 2026, 9:22 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Adobe Creative Cloud normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 389msstatus code: 401checked: Oct 19, 2026, 9:16 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Adobe Creative Cloud normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 653msstatus code: 401checked: Oct 19, 2026, 9:20 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Adobe Creative Cloud normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1927msstatus code: 401checked: Oct 19, 2026, 9:11 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Adobe Creative Cloud 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: 121msstatus code: 401checked: Oct 19, 2026, 9:27 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Adobe Creative Cloud normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 161msstatus code: 401checked: Oct 19, 2026, 9:17 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Adobe Creative Cloud 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: 1578msstatus code: 401checked: Oct 19, 2026, 9:20 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Adobe Creative Cloud normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1391msstatus code: 401checked: Oct 19, 2026, 9:20 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Adobe Creative Cloud normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 939msstatus code: 401checked: Oct 19, 2026, 9:24 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Adobe Creative Cloud 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 Adobe Creative Cloud, 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 have not received any reports for Adobe Creative Cloud yet, which is not evidence that nothing is wrong.

Recent probe events

No probe events on record yet for Adobe Creative Cloud.

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

We have been measuring Adobe Creative Cloud since August 20, 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 Adobe Creative Cloud covering any window you pick, with our check readings and Adobe Creative Cloud's own claim at the time, side by side.

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

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

Adobe Creative Cloud uptime by RealUptime's checksLive, from this page's own readings.
[![Adobe Creative Cloud uptime by RealUptime's checks](https://realuptime.io/outages/adobe-creative-cloud/badge.svg?days=30)](https://realuptime.io/outages/adobe-creative-cloud)
<a href="https://realuptime.io/outages/adobe-creative-cloud"><img src="https://realuptime.io/outages/adobe-creative-cloud/badge.svg?days=30" alt="Adobe Creative Cloud 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 Adobe Creative Cloud down?", https://realuptime.io/outages/adobe-creative-cloud. 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 Adobe Creative Cloud's stated SLA

At or above your target

Our checks of Adobe Creative Cloud 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 Adobe Creative Cloud'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

primaryfunctional: auth surface
https://ims-na1.adobelogin.com/ims/profile/v1
secondary
https://status.adobe.com/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: ims-na1.adobelogin.com

RealUptime is not affiliated with Adobe Creative Cloud; the name identifies what we checked, and nothing here speaks for Adobe Creative Cloud's own team. We send a single web request to Adobe Creative Cloud from 10 regions on our own schedule and time the response. We do not see inside Adobe Creative Cloud's systems, do not use an account or real transaction, and are not the same signal Adobe Creative Cloud's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Adobe Creative Cloud 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.