Observed topology
AS49774 INTERLINK-BANAT-AS S.C. Interlink Banat S.R.L.
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS49774: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS5483 | Magyar Telekom Plc. | Mobile | IPv4 IPv6 | 380 |
Transit
Downstream networks
Networks for which AS49774 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS31362 | NETPROTECT SRL | Unclassified | IPv4 | 58 |
| AS40984 | Bensoft Telecom SRL | Unclassified | IPv4 | 58 |
| AS211412 | Restart Energy One SA | Unclassified | IPv4 | 58 |
| AS62299 | Bluematrix Research LTD | Unclassified | IPv4 | 57 |
| AS50667 | NETPROTECT SRL | Unclassified | IPv4 | 54 |
| AS214529 | DAM TELECOM SERVICES SRL | Unclassified | IPv4 | 44 |
| AS61096 | Realmedia Network S.A. | Unclassified | IPv4 | 2 |
Adjacency
Adjacent networks
Every AS seen directly next to AS49774 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS5483 | Magyar Telekom Plc. | Mobile | IPv4 IPv6 | 722 |
| AS50667 | NETPROTECT SRL | Unclassified | IPv4 | 65 |
| AS31362 | NETPROTECT SRL | Unclassified | IPv4 | 58 |
| AS40984 | Bensoft Telecom SRL | Unclassified | IPv4 | 58 |
| AS211412 | Restart Energy One SA | Unclassified | IPv4 | 58 |
| AS62299 | Bluematrix Research LTD | Unclassified | IPv4 | 57 |
| AS214529 | DAM TELECOM SERVICES SRL | Unclassified | IPv4 | 44 |
| AS61096 | Realmedia Network S.A. | Unclassified | IPv4 | 2 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.
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. 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.
Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.