The rebranding is mostly complete. 47 production route servers are rebuilt and operational, and the ixFabric Portal and Looking Glass are now live.
The domain dispute is nearing completion, and return is currently expected within 5–10 days. Until ixFabric formally confirms that control has been restored, continue to treat the domain and any services or communications originating from it as potentially compromised.
Latest update
Updated 6 November 2026
The transition from BGP.Exchange to ixFabric is now mostly complete. Since our previous update, the rebuilt infrastructure and member-facing services have moved into active operation.
ixFabric now has 47 active production route servers, all rebuilt and operational. Our application, now known as the ixFabric Portal, is available at portal.ixfabric.net.
Our Looking Glass has also been rebuilt and relaunched at lg.ixfabric.net, providing a further public-facing service under the ixFabric identity.
The dispute concerning the bgp.exchange domain is nearing completion. Based on the current position, we expect the domain to be returned to us within the next 5–10 days. This remains an expectation rather than a confirmed transfer; we will publish a further announcement once control has formally been restored.
ixFabric rebranding and migration
The rebranding and migration from BGP.Exchange to ixFabric are now mostly complete. The project is operating under the ixFabric name, with the principal website, Portal and Looking Glass services available on the new domain.
Work to update records, service information and operational references across the organisations and databases used by the Internet routing community is continuing. This includes:
- Updating PeeringDB records and service information.
- Updating relevant APNIC records and objects.
- Updating relevant RIPE Database / WHOIS objects.
- Establishing and securing replacement routing registry objects where required.
- Updating network and peering references from BGP.Exchange to ixFabric.
- Updating DNS, email and web service identities.
- Updating application, member-facing services and operational documentation.
Some references to BGP.Exchange may remain visible while the remaining records and systems are progressively migrated. Members, peers and network operators should now expect ixFabric to be the primary identity across our infrastructure and public routing information.
bgp.exchange domain dispute
The bgp.exchange domain remains subject to the ongoing recovery process and has not yet been formally returned to our control.
The dispute is now nearing completion. Based on the current progress, we expect the domain to be returned to us within the next 5–10 days. This timeframe is an expectation only and remains subject to completion of the relevant registrar and registry processes.
Until we explicitly confirm that control has been restored, members, peers and partners should continue to treat the domain and any services or communications originating from it as potentially compromised.
Once recovery is formally confirmed, our intention is to have bgp.exchange redirect users to the official ixFabric website at ixfabric.net. We will announce the recovery through verified ixFabric communication channels before asking anyone to trust a redirect or other service operating under the domain.
Infrastructure recovery
The infrastructure rebuild has progressed from recovery and deployment into full production operation.
47 route servers are now active and operational in production. These route servers have been rebuilt as part of the recovery programme and are providing the core route-server services across the ixFabric network.
The replacement environment also includes:
- New authoritative DNS infrastructure.
- New mail relay and mail server infrastructure.
- New web server infrastructure.
- Operational application front-end and back-end services.
- New Docker infrastructure.
- A hardened replacement SQL database environment.
- The rebuilt and operational ixFabric Portal.
- The rebuilt and relaunched ixFabric Looking Glass.
These systems have been built within the redesigned environment rather than simply restoring the previous infrastructure.
Application security architecture
The application environment has undergone significant architectural changes as part of the rebuild.
Administrative functionality will no longer be available through the public or member-facing application environment.
Administrative functionality is being maintained within a separate secured environment with its own security boundary and access controls.
Protections include:
- Separation from the public member application.
- Dedicated administrative authentication.
- Mandatory multi-factor authentication.
- Rotating key-based security controls.
- Restricted network-level access.
- Additional logging and auditing of administrative activity.
The application code itself continues to undergo security and vulnerability review as part of preparations for the full ixFabric application launch.
Member accounts and passwords
Existing member passwords will not be carried forward for authentication against the relaunched application.
All previous member credentials will be invalidated as part of the ixFabric application launch.
Members will receive an individual password-reset process allowing them to establish a new password and validate access to their account before accessing the new platform.
This remains the case even though passwords in the previous platform were protected using Argon2id password hashing. Existing password hashes will not be relied upon for authentication within the relaunched environment.
Routing registry transition
Work is underway to update our routing registry and public network information to reflect the transition to ixFabric.
This includes updates to relevant PeeringDB, APNIC and RIPE Database / WHOIS records.
As previously advised, issues affecting the existing AS-SET will be addressed through the creation and securing of replacement objects as part of the ixFabric migration.
Where changes require action by members, peers or upstream networks, we will communicate the relevant information directly.
Investigation findings
Our investigation continues to indicate that the systems affected by the original incident were limited to:
- The application server.
- The database server.
- The email server.
- The previous Sydney hypervisor.
We have found no evidence that any route server, in any location worldwide, was accessed or compromised.
We have similarly found no evidence that hypervisors or infrastructure located at our other points of presence around the world were accessed as part of the incident.
Incident and recovery timeline
Current status
As at 6 November 2026, our current position is:
- The rebranding from BGP.Exchange to ixFabric is mostly complete.
- 47 rebuilt route servers are active and operational in production.
- The ixFabric Portal is live at portal.ixfabric.net.
- The rebuilt Looking Glass is live at lg.ixfabric.net.
- Remaining PeeringDB, APNIC, RIPE Database / WHOIS and routing registry updates are continuing.
- The bgp.exchange domain dispute is nearing completion, with return currently expected within 5–10 days.
- Until recovery is formally confirmed, bgp.exchange must continue to be treated as potentially compromised.
Moving forward as ixFabric
ixFabric is now operating under its new identity, with the majority of the rebranding and infrastructure recovery completed. The focus has shifted from rebuilding core services to ongoing operational improvements and completing the remaining transition work.
Our 47 production route servers are rebuilt and operational, and members and peers can access the ixFabric Portal and Looking Glass using the official ixFabric service endpoints.
We will continue updating PeeringDB entries, routing registry objects and other operational references so that the ixFabric identity is consistently reflected throughout the Internet routing community.
We expect the bgp.exchange domain to be returned within the next 5–10 days. Until ixFabric confirms that the transfer is complete, please continue to treat the domain as potentially compromised and rely only on our verified ixFabric channels for announcements and service links.
Following confirmed recovery, our intention is to redirect bgp.exchange to the official ixFabric website. We will communicate this change through verified channels before any redirect should be considered trusted.
We thank our members, peers, partners and infrastructure providers for their continued patience and support throughout the recovery and transition.