asn.dev

Observed topology

AS47377 ORANGE_BELGIUM_SA New company name is Orange Belgium SA

Upstreams 8 carry this network
Downstreams 9 this network carries
Adjacent (IPv4) 16
Adjacent (IPv6) 6

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS47377: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv63,459
AS5511Orange S.A.TransitIPv4 IPv6959
AS9002RETN LimitedUnclassifiedIPv4 IPv6701
AS6696VERIXI SAUnclassifiedIPv489
AS48185team.blue NVUnclassifiedIPv4 IPv689
AS29169GANDI SASHostingIPv486
AS6939Hurricane Electric LLCTransitIPv645
AS8218Zayo Infrastructure France SAUnclassifiedIPv63

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you.

Transit

Downstream networks

inferred

Networks for which AS47377 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS207467Orange Belgium SAUnclassifiedIPv4183
AS207232CHIREC asblUnclassifiedIPv498
AS34769Orange Communications Luxembourg S.AUnclassifiedIPv462
AS56369Orange Belgium SAUnclassifiedIPv462
AS12763Motor Europe Logistics NVUnclassifiedIPv461
AS201189IRC Engineering NVUnclassifiedIPv449
AS57933IRISnet SCRLUnclassifiedIPv421
AS204182Ministeries van de Vlaamse GemeenschapUnclassifiedIPv420
AS39855Mod Mission Critical LLCHostingIPv45

Adjacency

Adjacent networks

22 shown

Every AS seen directly next to AS47377 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv63,583
AS5511Orange S.A.TransitIPv4 IPv61,285
AS9002RETN LimitedUnclassifiedIPv4 IPv6777
AS207467Orange Belgium SAUnclassifiedIPv4183
AS6696VERIXI SAUnclassifiedIPv4101
AS48185team.blue NVUnclassifiedIPv4 IPv6101
AS207232CHIREC asblUnclassifiedIPv498
AS29169GANDI SASHostingIPv495
AS34769Orange Communications Luxembourg S.AUnclassifiedIPv462
AS56369Orange Belgium SAUnclassifiedIPv462
AS12763Motor Europe Logistics NVUnclassifiedIPv461
AS201189IRC Engineering NVUnclassifiedIPv449
AS6939Hurricane Electric LLCTransitIPv645
AS57933IRISnet SCRLUnclassifiedIPv421
AS204182Ministeries van de Vlaamse GemeenschapUnclassifiedIPv420
AS39855Mod Mission Critical LLCHostingIPv45
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv65

Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Interconnection

Exchange presence

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS47377, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider to carry traffic between them, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's own page, with its peering LANs and every other network recorded on it. Recorded at 1 exchange across 1 country and 1 region.

ExchangeLocationTheir addressMember ports
Belgian National Internet ExchangeBrussels, Belgium194.53.172.5882

Unlike the tables above, this is recorded rather than inferred. An address on a peering LAN is at that exchange by definition. Two carve-outs all the same. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. And an absent exchange means PCH has no record of it, not that the network is not there.

Provenance

Where this comes from

Derived from routing tables collected at 2026-08-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.02M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.

Exchange presence comes from a separate dataset: the directory collected 2026-08-08 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,137 recorded member ports, licensed CC BY-NC-SA 3.0.

PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.