---
service: "CData Cloud"
status: "up"
reports_last_hour: 0
reports_last_12_hours: 0
baseline_reports_per_hour: 0
checked_at: "2026-11-02T20:24:43.031Z"
url: "https://instatus.com/now/yo/cdata.com"
official_status_page: "https://status.cdata.com"
website: "http://cdata.com"
---

# Ṣé CData Cloud ti dásẹsẹ?

Rárá, ó ń ṣiṣẹ́. Ìròyìn 0 ní wákàtí tó kọjá.

## Àwọn ìmúdójúìwọ̀n aṣojú

- **Service Interruption: Arc Cloud/Sync Cloud - Azure Database Maintenance** (RESOLVED, 2026-11-01T05:10:31.000Z): Summary: Between 02:24 - 03:36 UTC on November 1, 2026, several customers experienced intermittent connectivity issues or total unavailability of their Arc Cloud and Sync Cloud instances. Our platform engineering team identified the cause as a scheduled maintenance and patching operation performed by our upstream cloud provider, Microsoft Azure, on the PostgreSQL database infrastructure. What Happened? Azure initiated a mandatory security and stability patch for the database clusters. During this process, the database instances underwent a restart to apply the updates. Arc Cloud instances re-established their database connections automatically within a few minutes. A subset of Sync Cloud instances did not reconnect on their own after the database returned and remained unavailable until they were restarted. Actions Taken: Immediate: Our Platform Engineering team monitored the recovery of all affected databases to ensure they returned to a "Healthy" state, and restarted the Sync Cloud instances that had not reconnected. Verification: We have verified that all customer data remains intact and that all application services have re-established connections. Sync jobs scheduled during the affected window may have failed and will run at their next scheduled time. Future Prevention: To minimize the impact of future provider maintenance, we are: Configuring custom maintenance windows on the database servers so provider patching occurs during the lowest-traffic period for our global customer base. Enhancing application-level connection retries to better handle transient provider restarts. We apologize for the disruption to your workflow!

## Àwọn ìbéèrè nípa ìdásẹ́sẹ̀ CData Cloud

### Ṣé CData Cloud ti dásẹsẹ báyìí?

Rárá, ó ń ṣiṣẹ́. Ìròyìn 0 ní wákàtí tó kọjá.

### Ṣé CData Cloud ti dásẹsẹ fún gbogbo ènìyàn tàbí èmi nìkan ni?

Ó dàbí ẹni pé ìwọ nìkan ni. Ìròyìn fún CData Cloud wà ní ìpele déédé, nítorí náà gbìyànjú láti tún-gbé e, ṣàyẹ̀wò ìsopọ̀ rẹ, tàbí jáde kí o tún wọlé.

### Àwọn ìṣòro wo ni àwọn ènìyàn ń ròyìn nípa CData Cloud?

Kò sí ẹni tó sọ ohun tó bàjẹ́ lórí CData Cloud ní wákàtí tó kọjá. Tí ohun kan kò bá ṣiṣẹ́ fún ọ, yàn án lókè kí àwọn míràn lè rí i.

### Ìgbà wo ni ìdásẹ́sẹ̀ CData Cloud gbẹ̀yìn?

Ìròyìn nípa CData Cloud kò gòkè ní ọgbọ̀n ọjọ́ tó kọjá.

### Ṣé CData Cloud ní ojú-ìwé ipò?

Bẹ́ẹ̀ ni. CData Cloud máa ń gbé àwọn ìmúdójúìwọ̀n sí ojú-ìwé ipò rẹ̀ tó jẹ́ ti ìjọba, èyí tó ń sọ báyìí pé: ń ṣiṣẹ́.

[Lọ sí ojú-ìwé ipò](https://status.cdata.com/)

### Kí ni mo lè ṣe tí CData Cloud kò bá ṣiṣẹ́?

Wo ojú-ìwé yìí àti ojú-ìwé ipò CData Cloud fún àwọn ìmúdójúìwọ̀n, kí o sì dúró fún ìṣẹ́jú díẹ̀ kí o tó gbìyànjú lẹ́ẹ̀kan sí i. Má ṣe tún-fi sórí ẹrọ: tó bá jẹ́ ìdásẹsẹ, àtúnṣe wà ní ọ̀dọ̀ wọn.

### Báwo ni mo ṣe lè fi ìṣòro CData Cloud ránṣẹ́?

Tẹ “Èmi náà ní ìṣòro” ní òkè ojú-ìwé yìí kí o sì yan ohun tó bàjẹ́. Ìròyìn rẹ máa hàn lórí àtẹ ìgbésààyè láàárín ìṣẹ́jú kan, o sì lè fi ọ̀rọ̀ sílẹ̀ láti sọ ohun tí o rí fún àwọn míràn.

### Báwo ni Instatus Now ṣe mọ̀?

A so ìròyìn àwọn ènìyàn ojú-ìwé yìí pọ̀ mọ́ ojú-ìwé ipò àṣẹ ti CData Cloud, tí a ń yẹ̀ wò ní ìṣẹ́jú kọ̀ọ̀kan.