What is Uplynk's uptime?

Over the last 90 days, Uplynk reported 99.41% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.uplynk.com, each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Uplynk's uptime history rolling forward in real time.

Has Uplynk had outages in 2026?

Yes, Uplynk has had 8 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.

When was the last Uplynk outage?

The most recent Uplynk incident was "Identified Issue Impacting Uplynk CMS Service", which started on October 28, 2026 and was resolved on October 28, 2026. Pingoru captured this directly from https://status.uplynk.com. See the full incident card above for affected components and the update timeline.

How often does Uplynk have outages?

Based on the last 90 days, Uplynk averages 2.7 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components: so you can see the pattern at a glance instead of digging through the vendor's archive.

Where is Uplynk's status page?

Uplynk's official status page is https://status.uplynk.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on, so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.

Is Uplynk down right now?

Uplynk is up. Pingoru checks the official status page every 5 minutes and flips this headline the moment Uplynk reports a change. Current status is based on 30 tracked services.

How does Pingoru know if Uplynk is down?

We read https://status.uplynk.com directly, using Uplynk's own status page. If the vendor reports an incident, you see it within one check cycle, not after someone manually marks the page as down.

Where can I get notified when Uplynk has an outage?

Create a free Pingoru account and add Uplynk as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.

Uplynk's status page says the service is up, but I'm having issues. What's wrong?

Three common reasons: • A real Uplynk incident that hasn't been acknowledged on their public status page yet, vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers. These rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Uplynk issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.

Where does Pingoru get the official Uplynk status?

We use Uplynk's own status page at https://status.uplynk.com and cross-reference their homepage (https://www.uplynk.com). Nothing is read in a way the vendor hasn't explicitly made public. We use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.

All tracked Uplynk components are reporting operational. No incidents are currently affecting service.

Is Uplynk down?

Last checked 3m ago

Current status

Uplynk is up

No incidents right now.

Get alerts when Uplynk breaks → View Uplynk outage history →

Free, no credit card

Official status page: status.uplynk.com
Checked every 5 minutes
30 components tracked

Uplynk is operational right now. Last checked 3m ago; the most recent incident resolved 3d ago.

Real-time Uplynk status, recent outages, and incident history: pulled directly from Uplynk's official status page at status.uplynk.com every 5 minutes. Pingoru tracks 30 Uplynk services and has captured 8 incidents in the last 90 days (99.41% uptime). Get email, Slack, Discord, or webhook alerts the moment Uplynk reports a new incident, free for 3 monitors, no credit card.

Users who monitor Uplynk also follow these CMS services:

Strapi View all 8,000+ providers

Uplynk uptime 99.41% uptime · past 90 days

Mon Wed Fri

AugSepOct

Less More

Recent outages & incidents

Past 90 days

Identified Issue Impacting Uplynk CMS Service

Resolved 48m

Started Oct 28, 2026, 04:06 PM UTC · Resolved Oct 28, 2026, 04:55 PM UTC

CMSCloudSlicerLive — Global
Timeline · 5 updates
- investigating · Oct 28, 2026, 04:06 PM UTC
  
  Uplynk Engineers have identified an issue impacting the Uplynk CMS portal, specifically navigating to the Ingest portion of the menu. Users may experience momentary issues navigating to that webpage section and rendering. Uplynk Streaming Ingest and Playback Services are not impacted. Engineers are actively working to resolve the issue. Next expected update: 20-30 minutes or as new information becomes available.
- investigating · Oct 28, 2026, 04:06 PM UTC
  
  Uplynk Engineers have identified an issue impacting the Uplynk CMS portal, specifically navigating to the Ingest portion of the menu. Users may experience momentary issues navigating to that webpage section and rendering. Uplynk Streaming Ingest and Playback Services are not impacted. Engineers are actively working to resolve the issue. Next expected update: 20-30 minutes or as new information becomes available.
- monitoring · Oct 28, 2026, 04:39 PM UTC
  
  Uplynk Engineers have identified an issue impacting the Ingest portion of the menu within the Uplynk CMS portal. Uplynk Streaming Ingest and Playback Services were not impacted. At this point, we have mitigated the issue impacting the Uplynk CMS Service. Our internal testing and monitoring tools are indicating that the platform is recovered. Users should begin to experience normal performance. Next expected update: 60 minutes or as new information becomes available.
- monitoring · Oct 28, 2026, 04:39 PM UTC
  
  Uplynk Engineers have identified an issue impacting the Ingest portion of the menu within the Uplynk CMS portal. Uplynk Streaming Ingest and Playback Services were not impacted. At this point, we have mitigated the issue impacting the Uplynk CMS Service. Our internal testing and monitoring tools are indicating that the platform is recovered. Users should begin to experience normal performance. Next expected update: 60 minutes or as new information becomes available.
- resolved · Oct 28, 2026, 04:55 PM UTC
  
  All Clear: Uplynk Engineers have fully resolved the issue impacting the Uplynk CMS Platform. Users should experience normal performance. Please contact our Support team if you require further assistance. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by text message Afghanistan [+93] Aland Islands [+358] Albania [+355] Algeria [+213] AmericanSamoa [+1 684] Andorra [+376] Angola [+244] Anguilla [+1 264] Antarctica [+672] Antigua and Barbuda [+1268] Argentina [+54] Armenia [+374] Aruba [+297] Australia [+61] Austria [+43] Azerbaijan [+994] Bahamas [+1 242] Bahrain [+973] Bangladesh [+880] Barbados [+1 246] Belarus [+375] Belgium [+32] Belize [+501] Benin [+229] Bermuda [+1 441] Bhutan [+975] Bolivia, Plurinational State of [+591] Bosnia and Herzegovina [+387] Botswana [+267] Brazil [+55] British Indian Ocean Territory [+246] Brunei Darussalam [+673] Bulgaria [+359] Burkina Faso [+226] Burundi [+257] Cambodia [+855] Cameroon [+237] Canada [+1] Cape Verde [+238] Cayman Islands [+ 345] Central African Republic [+236] Chad [+235] Chile [+56] China [+86] Christmas Island [+61] Cocos (Keeling) Islands [+61] Colombia [+57] Comoros [+269] Congo [+242] Congo, The Democratic Republic of the [+243] Cook Islands [+682] Costa Rica [+506] Cote d'Ivoire [+225] Croatia [+385] Cuba [+53] Cyprus [+537] Czech Republic [+420] Denmark [+45] Djibouti [+253] Dominica [+1 767] Dominican Republic [+1 849] Ecuador [+593] Egypt [+20] El Salvador [+503] Equatorial Guinea [+240] Eritrea [+291] Estonia [+372] Ethiopia [+251] Falkland Islands (Malvinas) [+500] Faroe Islands [+298] Fiji [+679] Finland [+358] France [+33] French Guiana [+594] French Polynesia [+689] Gabon [+241] Gambia [+220] Georgia [+995] Germany [+49] Ghana [+233] Gibraltar [+350] Greece [+30] Greenland [+299] Grenada [+1 473] Guadeloupe [+590] Guam [+1 671] Guatemala [+502] Guernsey [+44] Guinea [+224] Guinea-Bissau [+245] Guyana [+595] Haiti [+509] Holy See (Vatican City State) [+379] Honduras [+504] Hong Kong [+852] Hungary [+36] Iceland [+354] India [+91] Indonesia [+62] Iran, Islamic Republic of [+98] Iraq [+964] Ireland [+353] Isle of Man [+44] Israel [+972] Italy [+39] Jamaica [+1 876] Japan [+81] Jersey [+44] Jordan [+962] Kazakhstan [+7 7] Kenya [+254] Kiribati [+686] Korea, Democratic People's Republic of [+850] Korea, Republic of [+82] Kuwait [+965] Kyrgyzstan [+996] Lao People's Democratic Republic [+856] Latvia [+371] Lebanon [+961] Lesotho [+266] Liberia [+231] Libyan Arab Jamahiriya [+218] Liechtenstein [+423] Lithuania [+370] Luxembourg [+352] Macao [+853] Macedonia, The Former Yugoslav Republic of [+389] Madagascar [+261] Malawi [+265] Malaysia [+60] Maldives [+960] Mali [+223] Malta [+356] Marshall Islands [+692] Martinique [+596] Mauritania [+222] Mauritius [+230] Mayotte [+262] Mexico [+52] Micronesia, Federated States of [+691] Moldova, Republic of [+373] Monaco [+377] Mongolia [+976] Montenegro [+382] Montserrat [+1664] Morocco [+212] Mozambique [+258] Myanmar [+95] Namibia [+264] Nauru [+674] Nepal [+977] Netherlands [+31] Netherlands Antilles [+599] New Caledonia [+687] New Zealand [+64] Nicaragua [+505] Niger [+227] Nigeria [+234] Niue [+683] Norfolk Island [+672] Northern Mariana Islands [+1 670] Norway [+47] Oman [+968] Pakistan [+92] Palau [+680] Palestinian Territory, Occupied [+970] Panama [+507] Papua New Guinea [+675] Paraguay [+595] Peru [+51] Philippines [+63] Pitcairn [+872] Poland [+48] Portugal [+351] Puerto Rico [+1 939] Qatar [+974] Reunion [+262] Romania [+40] Russia [+7] Rwanda [+250] Saint Barthlemy [+590] Saint Helena, Ascension and Tristan Da Cunha [+290] Saint Kitts and Nevis [+1 869] Saint Lucia [+1 758] Saint Martin [+590] Saint Pierre and Miquelon [+508] Saint Vincent and the Grenadines [+1 784] Samoa [+685] San Marino [+378] Sao Tome and Principe [+239] Saudi Arabia [+966] Senegal [+221] Serbia [+381] Seychelles [+248] Sierra Leone [+232] Singapore [+65] Slovakia [+421] Slovenia [+386] Solomon Islands [+677] Somalia [+252] South Africa [+27] South Georgia and the South Sandwich Islands [+500] Spain [+34] Sri Lanka [+94] Sudan [+249] Suriname [+597] Svalbard and Jan Mayen [+47] Swaziland [+268] Sweden [+46] Switzerland [+41] Syrian Arab Republic [+963] Taiwan, Province of China [+886] Tajikistan [+992] Tanzania, United Republic of [+255] Thailand [+66] Timor-Leste [+670] Togo [+228] Tokelau [+690] Tonga [+676] Trinidad and Tobago [+1 868] Tunisia [+216] Turkey [+90] Turkmenistan [+993] Turks and Caicos Islands [+1 649] Tuvalu [+688] Uganda [+256] Ukraine [+380] United Arab Emirates [+971] United Kingdom [+44] United States [+1] Uruguay [+598] Uzbekistan [+998] Vanuatu [+678] Venezuela, Bolivarian Republic of [+58] Viet Nam [+84] Virgin Islands, British [+1 284] Virgin Islands, U.S. [+1 340] Wallis and Futuna [+681] Yemen [+967] Zambia [+260] Zimbabwe [+263] Example:
Latest: All Clear: Uplynk Engineers have fully resolved the issue impacting the Uplynk CMS Platform. Users should experience normal performance. Please contact our Support team if you requ…
Possible Issue with the Uplynk Clipping Tool

Resolved 6d

Started Oct 22, 2026, 04:16 PM UTC · Resolved Oct 28, 2026, 04:19 PM UTC

Clipping ToolCloudSlicerLive — Global
Timeline · 5 updates
- investigating · Oct 22, 2026, 04:16 PM UTC
  
  We are investigating an issue that might be impacting the Uplynk Clipping Tool. Uplynk Engineers are actively investigating customer impact, affected services, and remediation steps. Next expected update: 20-30 minutes or as new information becomes available.
- investigating · Oct 22, 2026, 04:16 PM UTC
  
  We are investigating an issue that might be impacting the Uplynk Clipping Tool. Uplynk Engineers are actively investigating customer impact, affected services, and remediation steps. Next expected update: 20-30 minutes or as new information becomes available.
- monitoring · Oct 22, 2026, 04:32 PM UTC
  
  The issue impacting asset loading within the clipping tool has been mitigated and service has been restored. Our engineering team identified the cause and implemented corrective actions. We are seeing normal platform operation and continue to monitor closely.
- monitoring · Oct 22, 2026, 04:32 PM UTC
  
  The issue impacting asset loading within the clipping tool has been mitigated and service has been restored. Our engineering team identified the cause and implemented corrective actions. We are seeing normal platform operation and continue to monitor closely.
- resolved · Oct 28, 2026, 04:19 PM UTC
  
  Clipping issue resolved. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by text message Afghanistan [+93] Aland Islands [+358] Albania [+355] Algeria [+213] AmericanSamoa [+1 684] Andorra [+376] Angola [+244] Anguilla [+1 264] Antarctica [+672] Antigua and Barbuda [+1268] Argentina [+54] Armenia [+374] Aruba [+297] Australia [+61] Austria [+43] Azerbaijan [+994] Bahamas [+1 242] Bahrain [+973] Bangladesh [+880] Barbados [+1 246] Belarus [+375] Belgium [+32] Belize [+501] Benin [+229] Bermuda [+1 441] Bhutan [+975] Bolivia, Plurinational State of [+591] Bosnia and Herzegovina [+387] Botswana [+267] Brazil [+55] British Indian Ocean Territory [+246] Brunei Darussalam [+673] Bulgaria [+359] Burkina Faso [+226] Burundi [+257] Cambodia [+855] Cameroon [+237] Canada [+1] Cape Verde [+238] Cayman Islands [+ 345] Central African Republic [+236] Chad [+235] Chile [+56] China [+86] Christmas Island [+61] Cocos (Keeling) Islands [+61] Colombia [+57] Comoros [+269] Congo [+242] Congo, The Democratic Republic of the [+243] Cook Islands [+682] Costa Rica [+506] Cote d'Ivoire [+225] Croatia [+385] Cuba [+53] Cyprus [+537] Czech Republic [+420] Denmark [+45] Djibouti [+253] Dominica [+1 767] Dominican Republic [+1 849] Ecuador [+593] Egypt [+20] El Salvador [+503] Equatorial Guinea [+240] Eritrea [+291] Estonia [+372] Ethiopia [+251] Falkland Islands (Malvinas) [+500] Faroe Islands [+298] Fiji [+679] Finland [+358] France [+33] French Guiana [+594] French Polynesia [+689] Gabon [+241] Gambia [+220] Georgia [+995] Germany [+49] Ghana [+233] Gibraltar [+350] Greece [+30] Greenland [+299] Grenada [+1 473] Guadeloupe [+590] Guam [+1 671] Guatemala [+502] Guernsey [+44] Guinea [+224] Guinea-Bissau [+245] Guyana [+595] Haiti [+509] Holy See (Vatican City State) [+379] Honduras [+504] Hong Kong [+852] Hungary [+36] Iceland [+354] India [+91] Indonesia [+62] Iran, Islamic Republic of [+98] Iraq [+964] Ireland [+353] Isle of Man [+44] Israel [+972] Italy [+39] Jamaica [+1 876] Japan [+81] Jersey [+44] Jordan [+962] Kazakhstan [+7 7] Kenya [+254] Kiribati [+686] Korea, Democratic People's Republic of [+850] Korea, Republic of [+82] Kuwait [+965] Kyrgyzstan [+996] Lao People's Democratic Republic [+856] Latvia [+371] Lebanon [+961] Lesotho [+266] Liberia [+231] Libyan Arab Jamahiriya [+218] Liechtenstein [+423] Lithuania [+370] Luxembourg [+352] Macao [+853] Macedonia, The Former Yugoslav Republic of [+389] Madagascar [+261] Malawi [+265] Malaysia [+60] Maldives [+960] Mali [+223] Malta [+356] Marshall Islands [+692] Martinique [+596] Mauritania [+222] Mauritius [+230] Mayotte [+262] Mexico [+52] Micronesia, Federated States of [+691] Moldova, Republic of [+373] Monaco [+377] Mongolia [+976] Montenegro [+382] Montserrat [+1664] Morocco [+212] Mozambique [+258] Myanmar [+95] Namibia [+264] Nauru [+674] Nepal [+977] Netherlands [+31] Netherlands Antilles [+599] New Caledonia [+687] New Zealand [+64] Nicaragua [+505] Niger [+227] Nigeria [+234] Niue [+683] Norfolk Island [+672] Northern Mariana Islands [+1 670] Norway [+47] Oman [+968] Pakistan [+92] Palau [+680] Palestinian Territory, Occupied [+970] Panama [+507] Papua New Guinea [+675] Paraguay [+595] Peru [+51] Philippines [+63] Pitcairn [+872] Poland [+48] Portugal [+351] Puerto Rico [+1 939] Qatar [+974] Reunion [+262] Romania [+40] Russia [+7] Rwanda [+250] Saint Barthlemy [+590] Saint Helena, Ascension and Tristan Da Cunha [+290] Saint Kitts and Nevis [+1 869] Saint Lucia [+1 758] Saint Martin [+590] Saint Pierre and Miquelon [+508] Saint Vincent and the Grenadines [+1 784] Samoa [+685] San Marino [+378] Sao Tome and Principe [+239] Saudi Arabia [+966] Senegal [+221] Serbia [+381] Seychelles [+248] Sierra Leone [+232] Singapore [+65] Slovakia [+421] Slovenia [+386] Solomon Islands [+677] Somalia [+252] South Africa [+27] South Georgia and the South Sandwich Islands [+500] Spain [+34] Sri Lanka [+94] Sudan [+249] Suriname [+597] Svalbard and Jan Mayen [+47] Swaziland [+268] Sweden [+46] Switzerland [+41] Syrian Arab Republic [+963] Taiwan, Province of China [+886] Tajikistan [+992] Tanzania, United Republic of [+255] Thailand [+66] Timor-Leste [+670] Togo [+228] Tokelau [+690] Tonga [+676] Trinidad and Tobago [+1 868] Tunisia [+216] Turkey [+90] Turkmenistan [+993] Turks and Caicos Islands [+1 649] Tuvalu [+688] Uganda [+256] Ukraine [+380] United Arab Emirates [+971] United Kingdom [+44] United States [+1] Uruguay [+598] Uzbekistan [+998] Vanuatu [+678] Venezuela, Bolivarian Republic of [+58] Viet Nam [+84] Virgin Islands, British [+1 284] Virgin Islands, U.S. [+1 340] Wallis and Futuna [+681] Yemen [+967] Zambia [+260] Zimbabwe [+263] Example: 201-555-1717 Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a
Latest: Clipping issue resolved. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create …
Possible Issue with Uplynk Playback, Uplynk Delivery, Uplynk Infrastructure, and Uplynk Ingest

Resolved 7d 1h

Started Oct 12, 2026, 06:01 PM UTC · Resolved Oct 19, 2026, 07:44 PM UTC

IngestPlaybackDeliveryDelivery — North AmericaInfrastructureCloudSlicerLive — Global
Timeline · 3 updates
- investigating · Oct 12, 2026, 06:01 PM UTC
  
  We are investigating an issue that might be impacting Uplynk Playback, Uplynk Delivery, Uplynk Infrastructure, and Uplynk Ingest. Uplynk Engineers are actively investigating customer impact, affected services, and remediation steps. Next expected update: 20-30 minutes or as new information becomes available.
- investigating · Oct 12, 2026, 06:01 PM UTC
  
  We are investigating an issue that might be impacting Uplynk Playback, Uplynk Delivery, Uplynk Infrastructure, and Uplynk Ingest. Uplynk Engineers are actively investigating customer impact, affected services, and remediation steps. Next expected update: 20-30 minutes or as new information becomes available.
- resolved · Oct 19, 2026, 07:44 PM UTC
  
  All Clear: Uplynk Engineers have fully resolved the issue impacting the Uplynk Streaming Platform. Users should experience normal performance. Please contact our Support team if you require further assistance. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by text message Afghanistan [+93] Aland Islands [+358] Albania [+355] Algeria [+213] AmericanSamoa [+1 684] Andorra [+376] Angola [+244] Anguilla [+1 264] Antarctica [+672] Antigua and Barbuda [+1268] Argentina [+54] Armenia [+374] Aruba [+297] Australia [+61] Austria [+43] Azerbaijan [+994] Bahamas [+1 242] Bahrain [+973] Bangladesh [+880] Barbados [+1 246] Belarus [+375] Belgium [+32] Belize [+501] Benin [+229] Bermuda [+1 441] Bhutan [+975] Bolivia, Plurinational State of [+591] Bosnia and Herzegovina [+387] Botswana [+267] Brazil [+55] British Indian Ocean Territory [+246] Brunei Darussalam [+673] Bulgaria [+359] Burkina Faso [+226] Burundi [+257] Cambodia [+855] Cameroon [+237] Canada [+1] Cape Verde [+238] Cayman Islands [+ 345] Central African Republic [+236] Chad [+235] Chile [+56] China [+86] Christmas Island [+61] Cocos (Keeling) Islands [+61] Colombia [+57] Comoros [+269] Congo [+242] Congo, The Democratic Republic of the [+243] Cook Islands [+682] Costa Rica [+506] Cote d'Ivoire [+225] Croatia [+385] Cuba [+53] Cyprus [+537] Czech Republic [+420] Denmark [+45] Djibouti [+253] Dominica [+1 767] Dominican Republic [+1 849] Ecuador [+593] Egypt [+20] El Salvador [+503] Equatorial Guinea [+240] Eritrea [+291] Estonia [+372] Ethiopia [+251] Falkland Islands (Malvinas) [+500] Faroe Islands [+298] Fiji [+679] Finland [+358] France [+33] French Guiana [+594] French Polynesia [+689] Gabon [+241] Gambia [+220] Georgia [+995] Germany [+49] Ghana [+233] Gibraltar [+350] Greece [+30] Greenland [+299] Grenada [+1 473] Guadeloupe [+590] Guam [+1 671] Guatemala [+502] Guernsey [+44] Guinea [+224] Guinea-Bissau [+245] Guyana [+595] Haiti [+509] Holy See (Vatican City State) [+379] Honduras [+504] Hong Kong [+852] Hungary [+36] Iceland [+354] India [+91] Indonesia [+62] Iran, Islamic Republic of [+98] Iraq [+964] Ireland [+353] Isle of Man [+44] Israel [+972] Italy [+39] Jamaica [+1 876] Japan [+81] Jersey [+44] Jordan [+962] Kazakhstan [+7 7] Kenya [+254] Kiribati [+686] Korea, Democratic People's Republic of [+850] Korea, Republic of [+82] Kuwait [+965] Kyrgyzstan [+996] Lao People's Democratic Republic [+856] Latvia [+371] Lebanon [+961] Lesotho [+266] Liberia [+231] Libyan Arab Jamahiriya [+218] Liechtenstein [+423] Lithuania [+370] Luxembourg [+352] Macao [+853] Macedonia, The Former Yugoslav Republic of [+389] Madagascar [+261] Malawi [+265] Malaysia [+60] Maldives [+960] Mali [+223] Malta [+356] Marshall Islands [+692] Martinique [+596] Mauritania [+222] Mauritius [+230] Mayotte [+262] Mexico [+52] Micronesia, Federated States of [+691] Moldova, Republic of [+373] Monaco [+377] Mongolia [+976] Montenegro [+382] Montserrat [+1664] Morocco [+212] Mozambique [+258] Myanmar [+95] Namibia [+264] Nauru [+674] Nepal [+977] Netherlands [+31] Netherlands Antilles [+599] New Caledonia [+687] New Zealand [+64] Nicaragua [+505] Niger [+227] Nigeria [+234] Niue [+683] Norfolk Island [+672] Northern Mariana Islands [+1 670] Norway [+47] Oman [+968] Pakistan [+92] Palau [+680] Palestinian Territory, Occupied [+970] Panama [+507] Papua New Guinea [+675] Paraguay [+595] Peru [+51] Philippines [+63] Pitcairn [+872] Poland [+48] Portugal [+351] Puerto Rico [+1 939] Qatar [+974] Reunion [+262] Romania [+40] Russia [+7] Rwanda [+250] Saint Barthlemy [+590] Saint Helena, Ascension and Tristan Da Cunha [+290] Saint Kitts and Nevis [+1 869] Saint Lucia [+1 758] Saint Martin [+590] Saint Pierre and Miquelon [+508] Saint Vincent and the Grenadines [+1 784] Samoa [+685] San Marino [+378] Sao Tome and Principe [+239] Saudi Arabia [+966] Senegal [+221] Serbia [+381] Seychelles [+248] Sierra Leone [+232] Singapore [+65] Slovakia [+421] Slovenia [+386] Solomon Islands [+677] Somalia [+252] South Africa [+27] South Georgia and the South Sandwich Islands [+500] Spain [+34] Sri Lanka [+94] Sudan [+249] Suriname [+597] Svalbard and Jan Mayen [+47] Swaziland [+268] Sweden [+46] Switzerland [+41] Syrian Arab Republic [+963] Taiwan, Province of China [+886] Tajikistan [+992] Tanzania, United Republic of [+255] Thailand [+66] Timor-Leste [+670] Togo [+228] Tokelau [+690] Tonga [+676] Trinidad and Tobago [+1 868] Tunisia [+216] Turkey [+90] Turkmenistan [+993] Turks and Caicos Islands [+1 649] Tuvalu [+688] Uganda [+256] Ukraine [+380] United Arab Emirates [+971] United Kingdom [+44] United States [+1] Uruguay [+598] Uzbekistan [+998] Vanuatu [+678] Venezuela, Bolivarian Republic of [+58] Viet Nam [+84] Virgin Islands, British [+1 284] Virgin Islands, U.S. [+1 340] Wallis and Futuna [+681] Yemen [+967] Zambia [+260] Zimbabwe [+263] Exa
Latest: All Clear: Uplynk Engineers have fully resolved the issue impacting the Uplynk Streaming Platform. Users should experience normal performance. Please contact our Support team if yo…

Incident record

Since April 2026 · Status.io · 30 components checked every 5 minutes

5incidents recorded

5last 12 months

3last 90 days

3 daystypical duration, 12 months

The longest incident in the last year, Possible Issue with Uplynk Playback, Uplynk Delivery, Uplynk Infrastructure, and Uplynk Ingest on October 12, 2026, ran for 7 days. 17 maintenance windows announced in the same period.

Most affected components, last 12 months

CloudSlicerLive — Global4
CMS2
Clipping Tool1
CloudSlicerLive1
Delivery1

Latest incidents

Identified Issue Impacting Uplynk CMS Service October 28, 2026 · 48 minutes · degraded service
Uplynk Engineers have identified an issue impacting the Uplynk CMS portal, specifically navigating to the Ingest portion of the menu. Users may experience…
Possible Issue with the Uplynk Clipping Tool October 22, 2026 · 6 days · degraded service
We are investigating an issue that might be impacting the Uplynk Clipping Tool. Uplynk Engineers are actively investigating customer impact, affected services…
Possible Issue with Uplynk Playback, Uplynk Delivery, Uplynk Infrastructure, and Uplynk Ingest October 12, 2026 · 7 days · degraded service
We are investigating an issue that might be impacting Uplynk Playback, Uplynk Delivery, Uplynk Infrastructure, and Uplynk Ingest. Uplynk Engineers are actively…

Outage history

Past 90 days · 3 incidents View full outage history →

Identified Issue Impacting Uplynk CMS Service Resolved

Started Oct 28, 2026, 04:06 PM UTC · Resolved Oct 28, 2026, 04:55 PM UTC · 48m
Possible Issue with the Uplynk Clipping Tool Resolved

Started Oct 22, 2026, 04:16 PM UTC · Resolved Oct 28, 2026, 04:19 PM UTC · 6d
Possible Issue with Uplynk Playback, Uplynk Delivery, Uplynk Infrastructure, and Uplynk Ingest Resolved

Started Oct 12, 2026, 06:01 PM UTC · Resolved Oct 19, 2026, 07:44 PM UTC · 7d 1h