Network overview
Start with the facts.
The public identifiers below make the network easy to find and independently verify.
- Autonomous system
- AS53902
- Registry
- ARIN
- IRR as-set
- AS-FLUXORUS
- Protocols listed
- IPv4 + IPv6
One public ASN. A clearer view.
Public routing reaches AS53902, then the Fluxorus service you use. Open the external records below to check current routes and network relationships.
Public routing records
Check the source.
Use these sources for current registration, routing, and prefix information.
AS53902
Fluxorus Networks
- ARINARIN RegistryASN registration and organization recordView
- PDBPeeringDBNetwork profile, policy, protocols, and contact dataView
- BGPBGP.toolsObserved routes, upstreams, and current RPKI stateView
- RADARCloudflare RadarPublic routing history and prefix observationsView
Registry and observed routing data can change. These links open the current public records rather than a cached status display.
Network questions
Before you deploy.
Review the public-network basics or contact us with a routing-specific question.
AS53902 is the autonomous system number registered to Fluxorus Networks. It identifies the network in public internet routing and registry records.
Use the linked ARIN, PeeringDB, BGP.tools, and Cloudflare Radar records. Those external sources are the better place to check current registration, observed routes, upstreams, and RPKI state.
No. It is a simplified architecture overview, not a monitoring dashboard. Use the linked routing records for current route and RPKI information.
The public PeeringDB profile lists both IPv4 and IPv6. Address assignment and availability can vary by product and location, so confirm the details shown during configuration.
Protection scope depends on the product and its service terms. Review the selected plan for included protection, or contact us when you need a specific filtering or remote-protection setup.
Contact our team with the ASN, prefixes, locations, and traffic requirements involved. We can confirm the current options and direct the request to the right network contact.
Choose the service that fits your workload.
Compare compute products or talk with the team about routing and deployment requirements.