BTW.Media
Daily editionStrategic Internet Intelligence
Sign InRegister

Briefing Desk

Latest Briefings

Concise reporting on the developments shaping internet governance and infrastructure. Browse each area for recent news, context and watchpoints.

Coverage

Market / Trends / Global Trends / Global Cloud Services Trends

In this section: 16 briefings

  1. Cloudflare’s IAD 5XX episode lasted 256 minutes but was disclosed in one retrospective update

    Cloudflare says an increased level of HTTP 5XX errors affected Ashburn, US (IAD), from 18:45 to 23:01 UTC on 31 July. Yet the public incident contains only one visible update, timestamped more than two hours after that interval ended. The fault is closed; the operational sequence, affected product and scale remain largely invisible.

  2. Twilio’s Claro Colombia short-code delay was still under investigation at the 20-minute cutoff

    Twilio opened a minor incident at 02:57:20.918 UTC on 1 August for SMS delivery delays from a subset of its short codes to Claro subscribers in Colombia. At the fixed 03:17:59 cutoff, 20 minutes and 38.082 seconds had elapsed. There was no identified cause, recovery signal or resolution to report.

  3. Anthropic closed a 47-minute Claude Sonnet 5 degradation with the service boundary still undisclosed

    Anthropic marked a minor Claude Sonnet 5 performance incident resolved at 07:04:49.691 UTC on 31 July, 46 minutes and 41.623 seconds after it opened. That short chronology establishes a start and an end, but almost nothing about the customer experience between them: no symptom, access surface, geography, request count or technical cause was published.

  4. Cloudflare’s us-east-1-aws path returned intermittent 5xx errors for 138 minutes

    Cloudflare resolved a minor incident involving intermittent HTTP 5xx responses for customers using the label us-east-1-aws at 04:19:32.991 UTC on 31 July. A fix had entered monitoring 10 minutes and 51.068 seconds earlier. The operator disclosed the request outcome and chronology, but not the Cloudflare product, exact error codes, affected volume or root cause.

  5. Twilio’s El Salvador incident delayed proof of SMS delivery, not necessarily the message

    For 9 hours, 41 minutes and 49.987 seconds on 31 July, Twilio tracked delayed SMS delivery receipts for messages sent toward Telefónica subscribers in El Salvador. Its most important qualification was present from the first notice: message delivery might succeed while the receipt arrived late. Service was declared normal at 16:17:09.745 UTC, but the cause and delay distribution remained private.

  6. A subset of Twilio numbers failed to deliver SMS to C+W LIME for more than 12 hours

    Twilio closed a minor SMS incident affecting a subset of its phone numbers on the route to C+W LIME subscribers in the Cayman Islands at 06:18:08.210 UTC on 31 July. The case had opened the previous day and lasted 12 hours, 27 minutes and 40.379 seconds. The narrow route and origin subset are public; the size of that subset, cause and retry outcomes are not.

  7. Twilio’s Celcom Malaysia SMS delay recovered without an identified public cause

    Twilio resolved a 3-hour, 21-minute and 39.361-second incident affecting SMS delivery toward Celcom subscribers in Malaysia at 02:12:32.051 UTC on 31 July. The case moved from investigation to observed recovery and then resolution; it never displayed an identified state. No delay distribution, message population or root cause was published.

  8. Twilio’s Claro Colombia voice incident changed its scope wording without measuring an expansion

    Twilio resolved a minor voice-call incident affecting a subset of origin numbers toward Claro subscribers in Colombia at 02:09:34.991 UTC on 31 July. During the 5-hour, 41-minute and 10.935-second case, “Mobile Numbers” became “Phone Numbers” and one update omitted Claro. The record never says those edits represented a wider technical footprint.

  9. Twilio was still monitoring Africell Angola SMS recovery after 25 hours at the cutoff

    Twilio had observed recovery in SMS delivery toward Africell subscribers in Angola four times by the fixed 00:13:55 UTC cutoff on 1 August. It had not declared the minor incident resolved. The public case had been open for 25 hours, 42 minutes and 51.122 seconds, while cause, delay distribution, message scale and the remaining condition stayed undisclosed.

  10. Twilio’s Brazil voice incident reached monitoring after 18 hours without a public cause

    Twilio said voice calls from its phone numbers to subscribers on multiple networks in Brazil were recovering on 31 July, but the incident was not resolved at the 20:19:07 UTC reporting cutoff. The first monitoring update came more than 18 hours after the case opened. Across that interval, the company acknowledged call failures and high post-dial delay, said it had identified the cause, and never disclosed what that cause was.

  11. Twilio’s RCS and WhatsApp queues recovered after a 99-minute delay incident

    Twilio recorded delays in both inbound and outbound delivery for RCS and WhatsApp on 31 July. The incident opened at 15:35:24.910 UTC, moved to monitoring at 16:44:39.656 and was declared resolved at 17:14:27.140. The chronology is clear; the scale and cause are not. Twilio disclosed neither a geography nor a message count, and “delay” does not establish loss, duplication or corruption.

  12. Zoom’s Whiteboard and Tasks incident recovered, then returned

    Zoom’s US-region status record shows two distinct degradation phases on 31 July. Users first lost the ability to list Zoom Whiteboards; Task creation was added to the affected scope fifteen minutes later. Both components entered monitoring at 12:45:35 UTC, and that was the state at this briefing’s 14:06:29 cutoff. Zoom then marked both services degraded again at 14:28:05, returned them to monitoring at 14:49:23 and closed the incident at 15:08:45. The record establishes a recurrence, but not its cause, reach or data impact.

  13. Cloudflare’s 70-minute incident separated its control plane from its edge

    Cloudflare recorded a minor incident at 11:51:07 UTC on 31 July, initially warning that Dashboard and related-API requests might fail while Analytics was degraded. The event later expanded to Pages and Worker builds, entered monitoring at 12:43:57 and was marked resolved at 13:01:59. Cloudflare explicitly said cached-file delivery through its CDN and other Edge security features were unaffected. That separation matters: customers lost reliable access to management and build functions without evidence that ordinary cached traffic stopped flowing.

  14. OpenAI resolved a short chat incident but left its failure domain unnamed

    OpenAI’s public incident record moved from identification at 09:04 UTC to mitigation at 09:06 and resolution at 09:28 on 31 July. The detailed update said some ChatGPT Business and Education users saw elevated errors when starting or continuing conversations. At this briefing’s fixed 09:23:13 window close, the incident was still in monitoring; the resolution arrived five minutes later and is included as an explicitly timed update. The visible status lifecycle lasted 24 minutes, but that is not necessarily the full customer-impact duration. OpenAI disclosed no failed component, cause, region, error rate, customer count or data-integrity effect.

  15. AWS is growing faster just as Amazon’s AI build turns free cash flow negative

    Amazon’s cloud business accelerated in the second quarter, while the group’s trailing free cash flow moved below zero. Those are not opposing stories. They are two stages of the same investment cycle. AWS sales rose 37% to $42.2 billion and segment operating income reached $16.6 billion, but Amazon reported a trailing $7.6 billion free-cash-flow outflow after purchases of property and equipment increased by $66.1 billion year on year, mainly reflecting AI investment. Management now expects about $220 billion of company-wide cash capital expenditure in 2026. The missing bridge is utilisation: how quickly expensive capacity becomes productive revenue and durable return.

  16. Meta’s invisible infrastructure queue has reached $279bn

    Meta spent $31.08 billion on capital equipment and finance-lease principal in the second quarter. The larger number is waiting outside the period’s visible expenditure: $278.99 billion of operating and finance lease obligations for data centres, colocation and certain network infrastructure that had not yet commenced at 30 June. Those contracts do not describe buildings already serving traffic, cash already paid or debt already recognised. They describe a supply queue that will begin at different points from the remainder of 2026 through 2036. A further $68 billion of data-centre leases signed in July shows that the queue was still accelerating after quarter-end. Meta is buying time and capacity before it needs both. The bargain protects access to scarce infrastructure, but commits future economics before utilisation, delivery and revenue have been demonstrated.

Coverage

Market / Trends / Global Trends / Global National Telecom Trends

In this section: 1 briefing

  1. Fénix promises a 14 Tbps Venezuela–Curaçao ring, but the cable is still an announced project

    Liberty Networks and CANTV announced Fénix on 31 July as a 378-kilometre submarine cable system between Camuri in Venezuela and Willemstad in Curaçao, with a stated minimum ring capacity of 14 Tbps. The design would connect Venezuela to a broader Caribbean hub. The release is evidence of a project launch, not of a cable already manufactured, laid, lit or carrying traffic.

Coverage

Market / Trends / Europe and Middle East Trends / Europe and Middle East Cloud Services Trends

In this section: 2 briefings

  1. Cloudflare’s London HTTP-error incident was still at the first diagnostic stage

    Cloudflare opened a minor incident at 19:06:19.068 UTC on 31 July after detecting increased HTTP errors affecting a subset of customers. Fourteen minutes later, at the Wave 46 cutoff, the public record still said only that the company was investigating, analysing and mitigating the problem. The London label locates the incident, but the notice did not name a facility, route, product, error code, cause or customer denominator.

  2. Cloudflare applied a fix in Hamburg, but the incident was still under watch at cutoff

    Cloudflare reported request errors or failures for customers whose traffic routed through its Hamburg location on 31 July. The company identified a problem at 15:20:19.991 UTC and said a fix was in place at 16:58:19.585. At the 17:49:33 Wave 45 cutoff, the incident remained in monitoring—not resolved. No affected product, traffic share, error rate or cause was disclosed.

Coverage

Market / Trends / Europe and Middle East Trends / Europe and Middle East National Telecom Trends

In this section: 1 briefing

  1. Hispasat’s Madrid teleport reaches WTA’s highest certification tier

    Hispasat’s Arganda del Rey teleport has entered the World Teleport Association registry at Tier 4 Full, the programme’s highest level. The certification gives customers an independently inspected signal about operational discipline at a ground facility that links satellite control, uplink and terrestrial connectivity. It does not publish the audit scorecard, guarantee uninterrupted service or replace performance evidence from the facility itself.

Coverage

Market / Trends / North America Trends / North America Datacenter Trends

In this section: 6 briefings

  1. Hamlet put 649 diesel engines through one public doorway

    More than 100 people attended a North Carolina hearing on two air-permit applications tied to Amazon’s Energy Way Tech Campus in Hamlet. One application covers 592 Amazon emergency engines—588 critical units and four ancillary units. The other covers 57 Duke Energy engines intended as temporary bridge power before the campus receives its permanent grid connection. The hearing joined those systems for public scrutiny, but the state must decide on them separately. No final permit had been issued, and the engine count is not evidence that every unit is installed or operating.

  2. Veolia takes the operating risk in Ohio’s 350MW private power island

    Veolia has been selected to operate and maintain a 350MW behind-the-meter microgrid for an undisclosed AI data-centre campus in Ohio. Gas engines and linear generators are expected to supply the campus, with a 430MWh battery supporting the system. The contract places Veolia at the point where a collection of power assets must become a continuously managed plant. It does not establish that 350MW of IT load is commissioned, that the availability target has been achieved or that an off-grid design removes fuel, emissions and equipment risks.

  3. A reported $15bn loan would make Anthropic’s Texas compute a test of Google’s balance-sheet reach

    The notable number in the reported financing talks for a data-centre campus in Hubbard, Texas, is not only the $15bn banks may lend. It is the obligation that could sit behind the debt. The Wall Street Journal reported that a Morgan Stanley-led consortium was discussing financing for Nexus Data Centers, while Google would guarantee billions of dollars of Anthropic’s lease and power commitments if the startup defaulted. Nothing in the public record shows that the financing has closed. Yet the proposed structure already reveals how AI infrastructure is moving beyond ordinary cloud procurement: lenders may be underwriting a chain that runs from a privately held model developer, through a project company and an onsite power plant, to the credit of a much larger technology group.

  4. Paducah’s proposed AI campus joins a $100bn headline to a 17bn-dollar cleanup ledger

    The U.S. Department of Energy has selected Brookfield Asset Management to develop and operate a proposed AI data-centre and energy complex at the government-owned Paducah Gaseous Diffusion Plant. AP reports a headline value of $100bn, with NextEra expected to build and own 2GW of gas generation, transmission upgrades and 2.6GW of battery storage for a 1.8GW AI campus. The site also carries a different long-duration number: a federal cleanup projected to continue to 2065 at about $17bn. Selection does not merge those obligations, approve the power agreement or identify the eventual computing customers. Kentucky’s lieutenant governor saying the governor’s office was not included in discussions exposes the missing governance layer between federal land, private capital and state-regulated electricity.

  5. Oregon cancelled the Salem land sale; Verrus says the data-centre proposal may still have another route

    Gov. Tina Kotek has directed Oregon’s Department of Administrative Services to terminate the state land-sale contract tied to Verrus’s proposed data-centre campus at Mill Creek Corporate Center in southeast Salem. The proposal had been described at about $5.1bn, with three data-centre buildings and a substation on roughly 75 acres. Losing the state parcel is a material failure of site control. It is not identical to a city denial: Salem said the project remained at an early stage, no formal development application had been filed, and data centres were then an allowed use in the Employment Center zone. Verrus’s assertion that the action may not stop the project therefore cannot be dismissed, but it also does not identify a replacement parcel, contract or approved plan.

  6. Southaven’s temporary turbine bridge finally has an exit calendar

    SpaceXAI says an agreed order with Mississippi regulators now sets dates for removing all 69 temporary mobile gas turbines at its Southaven power site: work may begin in August 2026 and is scheduled to finish by July 2027. In parallel, a permitted permanent plant designed for 1.2GW and 41 turbines is under construction. The timetable converts an improvised source of data-centre power into a transition that can be tested month by month. It does not show that any turbine has yet left the site, that the replacement plant is complete, or that a change from temporary to permanent generation will reduce emissions or noise.

Coverage

Market / Trends / Global Trends / Global Datacenter Trends

In this section: 10 briefings

  1. Nebius has disclosed the carbon cost of expansion, but not its full footprint

    Nebius reported 65,001 tonnes of market-based Scope 1 and 2 emissions for 2025, roughly 32 times the 2,036 tonnes disclosed a year earlier. The multiplication is striking, but its meaning depends on a changed operating base: the company says it expanded to seven active sites. The report makes the growth of operational emissions visible while leaving construction, hardware and much of the supply chain outside an uncompleted Scope 3 inventory.

  2. ENGIE’s 7GW data-centre number is two pipelines wearing the same unit

    ENGIE has moved a much larger share of its prospective data-centre work into an advanced stage: 4GW at the end of June, up from 0.8GW at the end of 2025. Together with 3GW at an early stage, that makes a 7GW project pipeline. Separately, the energy group also describes 7GW of power-purchase agreements with technology and data-centre companies. The matching number is a reporting hazard. One series tracks projects through development; the other tracks electricity contracts. Neither is 7GW of data centres already connected to a grid.

  3. CyrusOne appoints John Hatem as CEO

    John Hatem has taken over as CyrusOne CEO, widening his authority from commercial and project delivery functions to company-wide strategy.

  4. Veolia keeps €1bn data-centre and chip revenue target

    CyrusOne’s appointment of John Hatem keeps an executive who linked customer commitments to procurement and construction in charge of its next expansion phase.

  5. An Ohio automotive factory is being reassigned to the AI cooling cycle

    Mitsubishi Electric’s planned data-centre cooling plant in Mason, Ohio, begins with an asset from another industrial era: part of an existing automotive-electrical production site. The company will establish MEHITS US in August, invest approximately $30 million in renovation and equipment, and target production in April 2027. Reusing a factory can shorten construction and place manufacturing closer to customers, while Mitsubishi’s American power business can combine cooling with UPS and related systems. Yet the release contains no factory capacity, orders, customers, product mix, jobs or measured lead-time improvement. It is a supply-chain commitment, not evidence of delivered cooling capacity.

  6. Exelon has put a price on the difference between a data-centre request and a credible queue

    Exelon now describes about 11GW of prospective large load as “high probability”, but the useful disclosure is not the adjective or even the scale. It is the evidence underneath it. Projects in that group have reached advanced design or obtained FERC-approved Transmission Security Agreements; roughly 40% is covered by those agreements and about $1 billion of collateral. A separate 25GW remains in current or future cluster studies. The split turns an undifferentiated data-centre queue into stages of commitment. It still does not turn a request into an energised campus. Transmission design, generation supply, permits, construction and customer performance sit between collateral and delivered electricity, while Exelon’s existing $41.7 billion capital plan answers a different question from either load category.

  7. AEP is reserving turbines for a 69GW load book that has not reached the meter

    American Electric Power has begun matching contracts for future electricity demand with reservations for future generation equipment. It added 6GW of signed load agreements in the second quarter, primarily in Texas, taking contracted load growth through 2030 to 69GW. The customer set includes hyperscalers, data centres and industrial companies; it is not a 69GW measure of AI. On the supply side, AEP secured another 3GW of gas-turbine capacity, bringing equipment available for possible deployment through 2031 to about 13GW, while it evaluates a further 10GW through 2035. The parallel moves reduce two forms of optionality risk, but neither creates an operating power plant or a connected load. Contracts, equipment slots, permits, fuel, networks and metered demand remain separate tests.

  8. Europe’s AI gigafactory tender is a contract for demand

    The European Union has opened procurement for up to seven AI gigafactories, backed by as much as €10 billion of EU and national money and an expectation of at least €20 billion in private investment. The significant instrument is not the subsidy alone. EuroHPC and 18 Member States intend to buy compute access time from the selected operators. Europe is trying to make itself the first customer for an infrastructure class that private capital may otherwise judge too large, too power-hungry and too exposed to scarce accelerators. The tender converts sovereignty from a political ambition into a purchasing contract—without yet solving the price of electricity or dependence on American chips.

  9. Microsoft’s 88 data centres are a throughput claim, not a map

    Microsoft says it brought 31 new data centres online across five continents in its final fiscal quarter and 88 across the year. The larger revelation is not the pin count. In the same quarter it added another gigawatt of capacity, while cutting the time needed to move new GPUs from delivery dock to live service by nearly half over the year. Those are separate measurements of an AI infrastructure system: places, power, equipment velocity and capital. Reading them together shows why the bottleneck has shifted from announcing buildings to repeatedly turning expensive components into sellable cloud capacity.

  10. A management port is not a breach—but 24,650 pre-login replies redraw the risk

    Lava’s internet measurement does not show 24,650 compromised servers. It shows something more precise: 24,650 public IPMI endpoints returned password-derived authentication material before a client had authenticated. That distinction separates evidence from alarm. It also exposes a serious operating choice. A controller that can power a machine, open its console and mount virtual media was left reachable on the public internet, where password guessing can happen away from the defended host.

Coverage

Market / Trends / Asia-Pacific Trends / Asia-Pacific National Telecom Trends

In this section: 6 briefings

  1. Japan’s warning to LY Corporation is about a missing control path, not a data-sale finding

    Japan’s Ministry of Internal Affairs and Communications issued written administrative guidance to LY Corporation after a LINE game-development partner transmitted MID identifiers and other specified user information to a third-party analytics service. The ministry says the path operated without LY Corporation’s approval and without the required user notice or confirmation opportunity. It counted about 8.03 million records, including about 7.52 million associated with users in Japan. The notice does not say that messages, passwords or payment details were exposed, or that the information was sold.

  2. DOCOMO’s Ericsson choice moves the RAN bottleneck into compute

    NTT DOCOMO has selected Ericsson RAN Compute as a baseband platform spanning 4G, 5G and 5G-Advanced. The decision matters because radio capacity is increasingly governed by processing, pooling and software lifecycle as well as antennas. Ericsson says the new generation can provide up to twice the capacity of its predecessor while using less than half the energy. Those are vendor comparisons, not measured results for DOCOMO’s network, and the public report does not disclose how many units will be deployed or when.

  3. The Trans-Caspian cable has entered the seabed; it has not yet entered service

    A specialised vessel has departed Baku and begun laying fibre toward Aktau, converting the Trans-Caspian project from stored equipment into a physical route across the Caspian Sea. Kazakhstan’s government says regulatory, organisational and customs obstacles were resolved, a legal equipment-export list was established, and roughly 600 tonnes of armoured cable arrived through Port Kuryk before transfer into the cable ship. CaspiLink, the Kazakhtelecom–AzerTelecom joint venture, expects the direct lay to take 15–20 days if weather is favourable and the full project to be commissioned by the end of 2026. Those are separate milestones. Seabed installation proves construction activity, not accepted landings, lit capacity or traffic.

  4. Chinese localities expand data centres despite overbuild concerns

    China’s local data-centre push is expanding into towns and counties, raising questions over whether new computing capacity will attract enough demand.

  5. KT’s fine is 225 times the theft the regulator could count

    South Korea’s privacy regulator fined KT KRW53.979 billion after a rogue femtocell exposed identifiers belonging to 16,647 people and enabled about KRW240 million of unauthorised mobile payments. The arithmetic is striking: the fine is roughly 225 times the confirmed direct loss. It is not a compensation formula. It is the price of leaving an operator-controlled path from the network edge to the mobile core open for about 11 months, plus an order to rebuild the controls around it.

  6. Malaysia’s data-centre boom strains local resources

    Malaysia’s data-centre buildout is increasing pressure on power, water and communities, particularly in Johor, the country’s main development hub.

Coverage

Market / Trends / Asia-Pacific Trends / Asia-Pacific Datacenter Trends

In this section: 3 briefings

  1. LG Uplus has funded a 200MW destination, not switched it on

    LG’s additional KRW1.3tn commitment changes the financial scale of the Paju AI data-centre project. It does not change the physical state of the campus overnight. LG Uplus said in June that construction was about 20% complete and that a 200MW power supply had been secured; the new money therefore supports a defined route toward a very large facility rather than proving that 200MW of servers is already drawing power. The useful question is how capital, grid capacity, buildings and customers move through different clocks before a target completion in 2027.

  2. AirTrunk’s 400MW-plus SYD3 has a builder for its next phase, not a live meter

    Bouygues Construction’s €1.2bn contract for the next phase of AirTrunk’s SYD3 campus is a large, bounded construction event. Awarded through Australian subsidiary A W Edwards, it assigns work and a delivery horizon toward mid-2028. It does not establish the final cost of the campus or 400MW of operating capacity. The announced scale belongs to the expanded design; the contract belongs to one phase; customer use will arrive only after construction, power, commissioning and acceptance have crossed their own thresholds.

  3. India data-centre capacity forecast to reach 12GW by 2030

    Wood Mackenzie expects India’s data-centre capacity to reach 12GW by 2030, with power and water availability shaping where projects are delivered.

Coverage

Market / Trends / Europe and Middle East Trends / Europe and Middle East Datacenter Trends

In this section: 2 briefings

  1. Yondr is selling control of two Slough data centres without giving up the operating room

    Yondr has agreed to sell a majority interest in a UK data-centre campus to GLIL Infrastructure, while retaining a minority stake and responsibility for operational management after completion. The asset consists of two fully operational hyperscale buildings in Slough serving one leading hyperscale customer. This is not a clean exit and it is not yet a closed sale. It separates economic control from day-to-day operation at an asset that Yondr had already taken into the securitisation market. The price, exact share split, customer, governance rights and treatment of £532m in term notes remain undisclosed.

  2. Three ledgers turn Rolls-Royce’s data-centre power story into earnings

    Rolls-Royce Power Systems has moved data-centre demand beyond the language of pipeline and potential. Its half-year result now shows the theme in three separate ledgers: power-generation orders rose 55%, power-generation revenue rose 41%, and the division’s operating margin reached 20.3%. None is a data-centre-only number. Together, however, they show that supplying electricity around the compute hall is already changing the economics of an engine business.

Coverage

Market / Companies / Europe and Middle East Companies / Europe and Middle East National Telecom

In this section: 1 briefing

  1. CityFibre shareholders propose £900m equity injection

    CityFibre’s proposed funding ties network expansion and acquisitions to unresolved negotiations over its existing debt.

Coverage

Market / Trends / Africa Trends / Africa National Telecom Trends

In this section: 1 briefing

  1. UNITEL has contained a cyber incident; Angola is still waiting for a complete recovery ledger

    A national mobile network does not return with one switch. UNITEL says phased restoration of voice, data and internet began at 11:45 local time on 29 July after a cyberattack had disrupted those services across Angola. Its 30 July market notice described partial service in 13 provinces, SMS still unavailable and work continuing elsewhere. Hours later, Twilio was still reporting delivery delays and failures to UNITEL subscribers. The useful question is therefore not whether the attack is “under control”. It is which service works, where, at what quality, through which dependency, and for how long. Until UNITEL publishes that ledger, containment is an important milestone rather than proof of normal operation.

Coverage

Market / Trends / North America Trends / North America National Telecom Trends

In this section: 1 briefing

  1. FirstNet’s new 5G core moves public safety into a separate network decision room

    A different 5G symbol on an emergency worker’s handset would say little about who controls the connection. FirstNet’s consequential change is deeper in the network: subscribers have begun moving to a nationwide standalone 5G core dedicated to public safety and physically separate from AT&T’s commercial core. That core decides how sessions are authenticated, policies applied and traffic handled; multiple geographically distributed sites are intended to keep those functions available when one location is impaired. The launch is an architectural milestone, not a completed performance result. AT&T has not disclosed migration coverage, site locations, failover tests, measured latency or upload gains, and compatible devices and plans are still required.