AS273168INFRAESTRUCTURA Y REDES SAS
At a glance
IPv4 prefixes
0
IPv6 prefixes
17
IPv4 addresses
0
IPv6 /64s
1.1M
Upstream graph
The networks AS273168 is seen behind, one and two hops out, drawn from real AS paths.
AS273168Toward the internet core
Networks observed one and two hops upstream of AS273168 in real AS paths. A thicker line means more vantage points saw that adjacency, so weight tracks how well attested it is — not how much traffic it carries. Adjacency is an observation; whether it is a transit purchase or a settlement-free peering is an inference, and is labelled as one wherever we show it.
Neighbouring networks
24
adjacent networks
- Upstreams
- 1250%
- Peers
- 1250%
- Downstreams
- 00%
Networks carrying this one's traffic toward the rest of the internet.
| Network | Country | Relationship | Paths | Vantage pts |
|---|---|---|---|---|
| AS52468UFINET PANAMA S.A. | Peer | 247 | 62 | |
| AS267708SP SISTEMAS PALACIOS LTDA | Peer | 122 | 61 | |
| AS264646DOBLECLICK SOFTWARE E INGENERIA | Peer | 122 | 62 | |
| AS272869INTERCOMM DE NARIÑO SAS | Peer | 62 | 62 | |
| AS273102REDNET GROUP SAS | Peer | 62 | 62 | |
| AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BIC | Peer | 62 | 62 | |
| AS267777FUTURE SOLUTIONS DEVELOPMENT SAS | Peer | 62 | 62 | |
| AS267823ATENEA TELECOMUNICACIONES S.A.S | Peer | 61 | 61 | |
| AS272051POLINET TELECOMUNICACIONES COLOMBIA SAS | Peer | 61 | 61 | |
| AS269804SEPCOM COMUNICACIONES SAS | Peer | 61 | 61 |
Prefixes
The largest blocks AS273168 originates, widest first.
| Prefix | Addresses | Visibility |
|---|---|---|
| 2803:3250:ea19::/48 | 65.5k × /64 | 62/62 |
| 2803:3250:ea2d::/48 | 65.5k × /64 | 62/62 |
| 2803:3250:ea33::/48 | 65.5k × /64 | 60/62 |
| 2803:3250:ea34::/48 | 65.5k × /64 | 60/62 |
| 2803:3250:ea4a::/48 | 65.5k × /64 | 62/62 |
| 2803:3250:ea50::/48 | 65.5k × /64 | 61/62 |
| 2803:3250:ea72::/48 | 65.5k × /64 | 61/62 |
| 2803:3250:ea75::/48 | 65.5k × /64 | 61/62 |
| 2803:3250:ea7e::/48 | 65.5k × /64 | 62/62 |
| 2803:3250:ea81::/48 | 65.5k × /64 | 62/62 |
Routing data derived from RouteViews MRT archives, BGPKIT relationship inference and public registry data.