<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:news="http://www.google.com/schemas/sitemap-news/0.9">
  <url>
    <loc>https://btw.media/en/ntt-optqc-capital-alliance-million-qubit-roadmap</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>en</news:language>
      </news:publication>
      <news:publication_date>2026-08-03T04:47:00.000Z</news:publication_date>
      <news:title>NTT&apos;s OptQC pact adds capital to a roadmap, not a million-qubit machine</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/fr/ntt-optqc-alliance-capital-feuille-route-million-qubits</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>fr</news:language>
      </news:publication>
      <news:publication_date>2026-08-03T04:47:00.000Z</news:publication_date>
      <news:title>L&apos;alliance NTT-OptQC finance une trajectoire, pas encore une machine à un million de qubits</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/es/ntt-optqc-alianza-capital-ruta-millon-cubits</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>es</news:language>
      </news:publication>
      <news:publication_date>2026-08-03T04:47:00.000Z</news:publication_date>
      <news:title>La alianza NTT-OptQC financia una hoja de ruta, no una máquina ya construida de un millón de cúbits</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/zh/ntt-optqc-ziben-lianmeng-baiwan-liangzibi-luxiantu</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>zh-cn</news:language>
      </news:publication>
      <news:publication_date>2026-08-03T04:47:00.000Z</news:publication_date>
      <news:title>NTT 入股 OptQC 锁定的是协同路线图，不是一台现成的百万量子比特机器</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/ja/ntt-optqc-shusshi-hyakuman-ryoshi-bit-roadmap</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>ja</news:language>
      </news:publication>
      <news:publication_date>2026-08-03T04:47:00.000Z</news:publication_date>
      <news:title>NTT の OptQC 出資が買うのは、100万量子ビット機ではなく実装までの協働時間だ</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/pt-br/ntt-optqc-alianca-capital-roteiro-milhao-qubits</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>pt</news:language>
      </news:publication>
      <news:publication_date>2026-08-03T04:47:00.000Z</news:publication_date>
      <news:title>A aliança entre NTT e OptQC financia um roteiro, não um computador pronto de 1 milhão de qubits</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/ar/ntt-optqc-capital-alliance-million-qubit-ar</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>ar</news:language>
      </news:publication>
      <news:publication_date>2026-08-03T04:47:00.000Z</news:publication_date>
      <news:title>استثمار NTT في OptQC يمول خريطة طريق، لا حاسوباً جاهزاً بمليون كيوبت</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/de/ntt-optqc-kapitalallianz-millionen-qubit-fahrplan</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>de</news:language>
      </news:publication>
      <news:publication_date>2026-08-03T04:47:00.000Z</news:publication_date>
      <news:title>NTTs Einstieg bei OptQC finanziert einen Fahrplan, keine fertige Millionen-Qubit-Maschine</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/en/twilio-safaricom-kenya-sms-receipt-recovery</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>en</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T20:37:10.000Z</news:publication_date>
      <news:title>Twilio sees Safaricom Kenya receipt recovery after 57 minutes, but the cause stays undisclosed</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/fr/twilio-safaricom-kenya-recuperation-accuses-sms</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>fr</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T20:37:10.000Z</news:publication_date>
      <news:title>Chez Safaricom au Kenya, Twilio observe le retour des accusés sans clore l’incident</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/es/twilio-safaricom-kenia-recuperacion-recibos-sms</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>es</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T20:37:10.000Z</news:publication_date>
      <news:title>Twilio vigila la recuperación de los recibos SMS hacia Safaricom en Kenia</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/zh/twilio-safaricom-kenya-sms-receipts-recovery-zh</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>zh-cn</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T20:37:10.000Z</news:publication_date>
      <news:title>Twilio 称肯尼亚 Safaricom 短信回执已恢复，但事故尚未结案</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/ja/twilio-safaricom-kenya-sms-receipts-recovery-ja</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>ja</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T20:37:10.000Z</news:publication_date>
      <news:title>Twilio、ケニア Safaricom 向け SMS 受領通知の回復を確認障害は監視中</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/pt-br/twilio-safaricom-quenia-recuperacao-recibos-sms</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>pt</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T20:37:10.000Z</news:publication_date>
      <news:title>Twilio monitora recuperação de recibos de SMS para clientes Safaricom no Quênia</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/ar/twilio-safaricom-kenya-sms-receipts-recovery-ar</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>ar</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T20:37:10.000Z</news:publication_date>
      <news:title>Twilio تراقب تعافي إشعارات SMS إلى مشتركي Safaricom في كينيا</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/de/twilio-safaricom-kenia-sms-bestaetigungen-erholung</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>de</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T20:37:10.000Z</news:publication_date>
      <news:title>Twilio beobachtet Erholung der SMS-Bestätigungen zu Safaricom in Kenia</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/en/zoom-us-meeting-quality-operational-status</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>en</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T17:40:28.315Z</news:publication_date>
      <news:title>Zoom’s status entity kept Meetings operational while reporting degraded quality</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/fr/zoom-etats-unis-qualite-reunions-composant-operationnel</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>fr</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T17:40:28.315Z</news:publication_date>
      <news:title>Chez Zoom, le composant restait « opérationnel » malgré dix minutes de qualité dégradée</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/es/zoom-estados-unidos-calidad-reuniones-operativo</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>es</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T17:40:28.315Z</news:publication_date>
      <news:title>Zoom registró calidad degradada aunque Meetings siguió figurando como operativo</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/zh/zoom-meiguo-huiyi-zhiliang-zhuangtai-zhengchang</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>zh-cn</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T17:40:28.315Z</news:publication_date>
      <news:title>Zoom Meetings 状态保持正常，却承认部分美国用户会议质量下降</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/ja/zoom-us-meeting-quality-operational</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>ja</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T17:40:28.315Z</news:publication_date>
      <news:title>Zoom Meetings は「稼働中」のまま、一部利用者の品質低下を記録した</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/pt-br/zoom-eua-qualidade-reunioes-status-operacional</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>pt</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T17:40:28.315Z</news:publication_date>
      <news:title>Zoom manteve Meetings como operacional ao relatar queda na qualidade das reuniões</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/ar/zoom-us-meeting-quality-operational-ar</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>ar</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T17:40:28.315Z</news:publication_date>
      <news:title>Zoom أبقت Meetings في حالة تشغيلية رغم إقرارها بتراجع جودة الاجتماعات</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/de/zoom-usa-meeting-qualitaet-betriebsbereit</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>de</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T17:40:28.315Z</news:publication_date>
      <news:title>Zoom meldet schlechtere Meeting-Qualität bei weiterhin betriebsbereitem Meetings-Dienst</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/en/michigan-nine-water-systems-malicious-activity</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>en</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T16:32:08.569Z</news:publication_date>
      <news:title>Michigan’s nine water-system reports widen the cyber incident without showing unsafe water</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/fr/michigan-neuf-reseaux-eau-activite-malveillante</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>fr</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T16:32:08.569Z</news:publication_date>
      <news:title>Neuf réseaux d’eau du Michigan signalent une activité malveillante sans perte de sûreté sanitaire</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/es/michigan-nueve-sistemas-agua-actividad-maliciosa</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>es</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T16:32:08.569Z</news:publication_date>
      <news:title>Nueve sistemas de agua de Michigan reportan actividad maliciosa sin perder la operación segura</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/zh/michigan-jiu-ge-gongshui-xitong-eyi-huodong</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>zh-cn</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T16:32:08.569Z</news:publication_date>
      <news:title>密歇根州九个供水系统报告恶意活动，但安全供水并未中断</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/ja/michigan-water-systems-cyber-activity</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>ja</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T16:32:08.569Z</news:publication_date>
      <news:title>ミシガン州の水道9系統で悪意ある活動、安全な運転は維持</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/pt-br/michigan-nove-sistemas-agua-atividade-maliciosa</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>pt</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T16:32:08.569Z</news:publication_date>
      <news:title>Nove sistemas de água de Michigan registram atividade maliciosa, mas mantêm operação segura</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/ar/michigan-nine-water-systems-cyber-ar</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>ar</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T16:32:08.569Z</news:publication_date>
      <news:title>نشاط خبيث يطال تسعة أنظمة مياه في Michigan من دون فقدان التشغيل الآمن</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/de/michigan-neun-wassersysteme-boesartige-aktivitaet</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>de</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T16:32:08.569Z</news:publication_date>
      <news:title>Neun Wassersysteme in Michigan melden bösartige Aktivität bei weiter sicherem Betrieb</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/en/twilio-safaricom-kenya-sms-routes-monitoring</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>en</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T16:32:08.569Z</news:publication_date>
      <news:title>Twilio saw recovery on a subset of SMS routes to Safaricom, but had not closed the incident</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/fr/twilio-safaricom-kenya-sms-reprise-surveillance</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>fr</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T16:32:08.569Z</news:publication_date>
      <news:title>Twilio observe la reprise d’une partie des SMS vers Safaricom sans encore clore l’incident</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/es/twilio-safaricom-kenia-sms-recuperacion-vigilancia</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>es</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T16:32:08.569Z</news:publication_date>
      <news:title>Twilio observa recuperación parcial de SMS hacia Safaricom, pero el incidente seguía abierto</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/zh/twilio-safaricom-kenya-duanxin-huifu-jiance</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>zh-cn</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T16:32:08.569Z</news:publication_date>
      <news:title>Twilio 至 Safaricom 的部分短信路径开始恢复，但事件尚未关闭</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/ja/twilio-safaricom-kenya-sms-recovery-monitoring</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>ja</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T16:32:08.569Z</news:publication_date>
      <news:title>Twilio から Safaricom への一部 SMS 経路は回復、事案は監視中</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/pt-br/twilio-safaricom-quenia-sms-recuperacao-monitoramento</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>pt</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T16:32:08.569Z</news:publication_date>
      <news:title>Twilio observa recuperação parcial de SMS para a Safaricom, mas mantém o incidente aberto</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/ar/twilio-safaricom-kenya-sms-recovery-ar</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>ar</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T16:32:08.569Z</news:publication_date>
      <news:title>Twilio ترصد تعافي بعض مسارات الرسائل إلى Safaricom من دون إغلاق الحادث</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/de/twilio-safaricom-kenia-sms-erholung-monitoring</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>de</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T16:32:08.569Z</news:publication_date>
      <news:title>Twilio sieht Erholung auf einzelnen SMS-Routen zu Safaricom, hält den Vorfall aber offen</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/en/eu-ai-act-article-50-transparency-duties-apply</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>en</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T16:32:08.569Z</news:publication_date>
      <news:title>EU AI transparency duties take effect with separate obligations for providers and deployers</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/fr/ue-ai-act-article-50-obligations-transparence</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>fr</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T16:32:08.569Z</news:publication_date>
      <news:title>Les obligations européennes de transparence de l’IA entrent en vigueur selon le rôle de chaque acteur</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/es/ue-ley-ia-articulo-50-obligaciones-transparencia</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>es</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T16:32:08.569Z</news:publication_date>
      <news:title>Entran en vigor las obligaciones europeas de transparencia para proveedores y usuarios de IA</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/zh/eu-ai-act-di-50-tiao-toumingdu-yiwu-shengxiao</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>zh-cn</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T16:32:08.569Z</news:publication_date>
      <news:title>欧盟 AI 透明度义务正式适用，提供方与部署方责任分开</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/ja/eu-ai-act-article-50-transparency-obligations</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>ja</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T16:32:08.569Z</news:publication_date>
      <news:title>EU の AI 透明性義務が適用開始、提供者と導入者で責任を分担</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/pt-br/ue-ai-act-artigo-50-deveres-transparencia</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>pt</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T16:32:08.569Z</news:publication_date>
      <news:title>Deveres europeus de transparência em IA passam a valer com responsabilidades separadas</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/ar/eu-ai-act-article-50-transparency-ar</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>ar</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T16:32:08.569Z</news:publication_date>
      <news:title>بدء التزامات شفافية الذكاء الاصطناعي في الاتحاد الأوروبي مع توزيع المسؤولية</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/de/eu-ai-act-artikel-50-transparenzpflichten</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>de</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T16:32:08.569Z</news:publication_date>
      <news:title>EU-Transparenzpflichten für KI gelten nun getrennt für Anbieter und Betreiber</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/en/zoom-marketplace-ai-companion-retrospective-degradation</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>en</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T03:08:24.248Z</news:publication_date>
      <news:title>Zoom disclosed a 76-minute Marketplace and AI Companion degradation only after it had ended</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/fr/zoom-marketplace-ai-companion-degradation-retrospective</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>fr</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T03:08:24.248Z</news:publication_date>
      <news:title>Chez Zoom, 76 minutes de service dégradé précèdent de 29 minutes la première trace publique</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/es/zoom-marketplace-ai-companion-degradacion-retrospectiva</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>es</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T03:08:24.248Z</news:publication_date>
      <news:title>Zoom cerró en 16 minutos un registro que describía 76 minutos de degradación ya terminada</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/zh/zoom-marketplace-ai-companion-shihou-jiangji</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>zh-cn</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T03:08:24.248Z</news:publication_date>
      <news:title>Zoom 在服务恢复约 29 分钟后，才公开 Marketplace 与 AI Companion 降级记录</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/ja/zoom-marketplace-ai-companion-jigo-kaiji</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>ja</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T03:08:24.248Z</news:publication_date>
      <news:title>Zoom、Marketplace と AI Companion の76分間の機能低下を終了後に公表</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/pt-br/zoom-marketplace-ai-companion-degradacao-retrospectiva</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>pt</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T03:08:24.248Z</news:publication_date>
      <news:title>Zoom revelou só depois uma degradação de 76 minutos no Marketplace e no AI Companion</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/ar/zoom-marketplace-ai-companion-retrospective-degradation-ar</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>ar</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T03:08:24.248Z</news:publication_date>
      <news:title>Zoom كشفت بعد انتهاء الخلل عن 76 دقيقة من تراجع Marketplace وAI Companion</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/de/zoom-marketplace-ai-companion-nachtraegliche-stoerung</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>de</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T03:08:24.248Z</news:publication_date>
      <news:title>Zoom veröffentlichte die 76-minütige Störung von Marketplace und AI Companion erst im Nachhinein</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/en/cloudflare-istanbul-15-minute-network-incident</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>en</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>Cloudflare’s 15-minute Istanbul network incident left a precise window but almost no diagnosis</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/fr/cloudflare-istanbul-incident-reseau-15-minutes</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>fr</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>À Istanbul, Cloudflare borne l’incident à quinze minutes sans en révéler le mécanisme</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/es/cloudflare-estambul-incidente-red-15-minutos</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>es</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>Cloudflare acotó a 15 minutos la degradación de Estambul, pero dejó sin explicar su alcance</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/zh/cloudflare-yisitanbuer-15-fenzhong-wangluo-shijian</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>zh-cn</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>Cloudflare 精确标出伊斯坦布尔 15 分钟异常，却没有交代故障发生在哪一层</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/ja/cloudflare-istanbul-15fun-network-incident</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>ja</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>Cloudflare のイスタンブール障害、15分という精密な枠だけが残り原因と規模は空白</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/pt-br/cloudflare-istambul-incidente-rede-15-minutos</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>pt</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>Cloudflare delimitou a falha de Istambul a 15 minutos, mas não mostrou onde ela ocorreu</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/ar/cloudflare-istanbul-network-incident-ar</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>ar</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>حدّدت Cloudflare اضطراب إسطنبول في 15 دقيقة وتركت طبقة العطل وحجمه بلا تفسير</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/de/cloudflare-istanbul-netzwerkstoerung-15-minuten</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>de</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>Cloudflare grenzte die Störung in Istanbul auf 15 Minuten ein, ließ Ursache und Umfang aber offen</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/en/github-luna-gpt-5-6-upstream-degradation</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>en</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>GitHub restored GPT-5.6 Luna after 74 minutes, but the incident exposes a model-routing dependency</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/fr/github-luna-gpt-5-6-degradation-fournisseur-amont</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>fr</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>La panne de GPT-5.6 Luna montre que la continuité de Copilot dépend aussi du routage entre modèles</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/es/github-luna-gpt-5-6-degradacion-proveedor-ascendente</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>es</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>La degradación de GPT-5.6 Luna convirtió la selección de modelo en una ruta de contingencia</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/zh/github-luna-gpt-5-6-shangyou-fuwu-jiangji</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>zh-cn</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>GPT-5.6 Luna 恢复前，GitHub 把“换模型”变成了 Copilot 的连续性方案</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/ja/github-luna-gpt-5-6-joryu-provider-shogai</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>ja</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>GitHub の GPT-5.6 Luna 障害、モデル選択そのものが Copilot の迂回路になった</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/pt-br/github-luna-gpt-5-6-degradacao-provedor</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>pt</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>Falha do GPT-5.6 Luna fez da escolha de modelo uma camada de continuidade do Copilot</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/ar/github-luna-gpt-5-6-upstream-degradation-ar</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>ar</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>كشف تعطل GPT-5.6 Luna أن اختيار النموذج أصبح مسار استمرارية داخل Copilot</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/de/github-luna-gpt-5-6-upstream-stoerung</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>de</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>Bei der GPT-5.6-Luna-Störung wurde die Modellwahl selbst zum Ausweichpfad für Copilot</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/en/twilio-globe-philippines-delivery-receipt-delays</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>en</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>Twilio’s Globe Philippines incident delayed the receipt signal, not necessarily the SMS</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/fr/twilio-globe-philippines-retards-accuses-reception</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>fr</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>Chez Twilio, le retard concernait l’accusé de livraison vers Globe, pas nécessairement le SMS</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/es/twilio-globe-filipinas-retrasos-recibos-entrega</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>es</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>Twilio retrasó la confirmación hacia Globe Filipinas, aunque el SMS podía haber llegado</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/zh/twilio-feilvbin-globe-songda-huizhi-yanchi</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>zh-cn</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>Twilio 事件延迟的是 Globe 菲律宾短信回执，不能据此认定短信没有送达</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/ja/twilio-philippines-globe-delivery-receipt-delay</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>ja</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>Twilio と Globe の障害で遅れたのは SMS そのものではなく配信確認だった</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/pt-br/twilio-globe-filipinas-atrasos-recibos-entrega</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>pt</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>Na rota da Globe nas Filipinas, a Twilio perdeu pontualidade na confirmação, não necessariamente no SMS</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/ar/twilio-globe-philippines-delivery-receipts-ar</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>ar</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>تأخر إشعار التسليم بين Twilio وGlobe في الفلبين لا يثبت أن الرسالة لم تصل</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/de/twilio-globe-philippinen-zustellberichte-verzoegert</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>de</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>Bei Twilio und Globe verspätete sich das Zustellsignal, nicht zwingend die SMS</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/en/cloudflare-realtimekit-sockets-meeting-joins-incident</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>en</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>Cloudflare’s RealtimeKit join failures lasted 65 minutes, while its incident metadata says otherwise</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/fr/cloudflare-realtimekit-sockets-jonction-reunions-incident</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>fr</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>RealtimeKit: Cloudflare décrit 65 minutes d’échec à l’entrée, mais ses métadonnées ferment l’incident dès le départ</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/es/cloudflare-realtimekit-sockets-union-reuniones-incidente</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>es</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>RealtimeKit sufrió 65 minutos de problemas de acceso que no caben en los metadatos de Cloudflare</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/zh/cloudflare-realtimekit-socket-huiyi-jiaru-shijian</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>zh-cn</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>RealtimeKit 会议加入故障持续 65 分钟，Cloudflare 元数据却在起点就写下“已解决”</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/ja/cloudflare-realtimekit-socket-meeting-join-incident</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>ja</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>RealtimeKit の参加障害は65分、Cloudflare のメタデータは開始時点で解決済み</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/pt-br/cloudflare-realtimekit-sockets-entrada-reunioes-incidente</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>pt</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>RealtimeKit teve 65 minutos de falha na entrada, mas os metadados encerram o caso no começo</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/ar/cloudflare-realtimekit-meeting-joins-incident-ar</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>ar</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>استمر تعطل دخول RealtimeKit 65 دقيقة بينما تغلق البيانات الواقعة عند بدايتها</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/de/cloudflare-realtimekit-sockets-meeting-beitritt-stoerung</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>de</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>RealtimeKit meldet 65 Minuten Join-Probleme, doch Cloudflares Metadaten schließen den Fall am Anfang</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/en/github-fable-5-upstream-provider-incident</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>en</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>GitHub took 17 minutes to name Fable 5 after upstream model errors began</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/fr/github-fable-5-incident-fournisseur-amont</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>fr</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>GitHub a mis dix-sept minutes à passer d’erreurs amont génériques au modèle Fable 5</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/es/github-fable-5-incidente-proveedor-ascendente</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>es</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>El segundo incidente de modelos de GitHub tardó 17 minutos en señalar a Fable 5</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/zh/github-fable-5-shangyou-gongyingshang-shijian</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>zh-cn</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>GitHub 先看到上游错误，17 分钟后才把 Fable 5 写进事件记录</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/ja/github-fable-5-joryu-provider-incident</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>ja</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>GitHub は上流エラー検知から17分後に Fable 5を特定した</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/pt-br/github-fable-5-incidente-provedor</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>pt</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>GitHub levou 17 minutos para transformar erros upstream em um alerta específico sobre Fable 5</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/ar/github-fable-5-upstream-provider-incident-ar</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>ar</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>احتاجت GitHub إلى 17 دقيقة للانتقال من أخطاء منبع عامة إلى تسمية Fable 5</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://btw.media/de/github-fable-5-upstream-provider-stoerung</loc>
    <news:news>
      <news:publication>
        <news:name>BTW Media</news:name>
        <news:language>de</news:language>
      </news:publication>
      <news:publication_date>2026-08-02T02:07:00.711Z</news:publication_date>
      <news:title>GitHub brauchte 17 Minuten, um aus Upstream-Fehlern den betroffenen Fable-5-Pfad zu benennen</news:title>
    </news:news>
  </url>
</urlset>