Skip to main content

AS273976

273976

Autonomous System AS273976 from PE-FTSA1-LACNIC

Registry

Authoritative registration data

AS number
273976
Name
273976
Organisation
Autonomous System AS273976 from PE-FTSA1-LACNIC
Country
—
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

11

IPv6 prefixes

5

Total announced

16

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS273976
190.93.224.0/22 IPv4 /22 not checked
170.62.156.0/23 IPv4 /23 not checked
190.93.224.0/23 IPv4 /23 not checked
190.93.226.0/23 IPv4 /23 not checked
190.93.224.0/24 IPv4 /24 not checked
190.93.225.0/24 IPv4 /24 not checked
190.93.226.0/24 IPv4 /24 not checked
190.93.227.0/24 IPv4 /24 not checked
38.252.217.0/24 IPv4 /24 not checked
45.166.72.0/24 IPv4 /24 not checked
92.118.181.0/24 IPv4 /24 not checked
2803:b0d0::/32 IPv6 /32 RPKI not found
2803:b0d0:5f00::/40 IPv6 /40 RPKI not found
2803:b0d0:fc00::/40 IPv6 /40 not checked
2803:b0d0:ff00::/40 IPv6 /40 not checked
2803:b0d0::/48 IPv6 /48 RPKI not found

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS273976
Address families
Chile IX by PIT.net 100,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA 10,000 Mbps IPv4 · IPv6
PIT - Argentina - Buenos Aires 100,000 Mbps IPv4 · IPv6
PIT - Colombia - Barranquilla 100,000 Mbps IPv4 · IPv6
PIT - Colombia - Bogota 10,000 Mbps IPv4 · IPv6
PIT - Colombia - Cali 10,000 Mbps IPv4 · IPv6
PIT - Colombia - Medellin 10,000 Mbps IPv4 · IPv6
PIT - Ecuador - Quito 100,000 Mbps IPv4 · IPv6
PIT - Peru - Lima: Main 100,000 Mbps IPv4 · IPv6
PIT Santiago - PIT Chile: LAN 10,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS273976 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS273976 in AS paths

Observed upstreams
Families
AS3356 LEVEL3 3,378 11,870
v4 v6
AS7195 7195 1,294 3,846
v4 v6
AS263237 263237 516 976
v4 v6
AS6762 SEABONE-NET 212 774
v4 v6
AS6057 6057 38 160
v4 v6
AS21575 21575 13 39
v4
AS61626 ASN61626 12 22
v4 v6
AS52320 52320 5 8
v4 v6
AS273478 ASN273478 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

15 networks seen after AS273976 in AS paths

Observed downstreams
Families
AS273946 273946 332 3,379
v4 v6
AS264783 264783 524 2,786
v4 v6
AS269843 269843 1,143 2,665
v4 v6
AS273914 273914 440 1,366
v4 v6
AS274131 274131 386 846
v4 v6
AS274156 274156 285 735
v4 v6
AS273018 273018 315 708
v4 v6
AS272877 272877 254 578
v4 v6
AS273014 273014 400 562
v4 v6
AS273112 273112 148 309
v4 v6
AS272836 272836 228 285
v4
AS266716 266716 226 277
v4
AS273883 273883 171 263
v4 v6
AS270037 270037 3 36
v4 v6
AS273103 273103 17 22
v4

No rows match “”.

Showing – of

Uncertain adjacencies

20 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS14840 ASN14840 21 292
v4 v6
AS24482 SGGS-AS-AP 21 144
v4 v6
AS51185 MAINSTREAMING-AS 22 104
v4 v6
AS22548 ASN22548 21 75
v4 v6
AS28624 ASN28624 21 75
v4 v6
AS60503 FNXTEC 21 74
v4 v6
AS6424 EDGOO 21 73
v4 v6
AS271253 ASN271253 15 69
v4
AS28634 ASN28634 13 60
v4
AS52873 ASN52873 11 47
v4 v6
AS199524 GCORE 11 47
v4 v6
AS263702 263702 8 41
v6
AS264479 ASN264479 11 36
v4 v6
AS263152 ASN263152 9 29
v4 v6
AS36236 NETACTUATE 4 28
v4 v6
AS37721 ORG-VTS1-AFRINIC 12 23
v4 v6
AS35280 F5 9 22
v6
AS262427 ASN262427 4 12
v4
AS49544 i3Dnet 1 11
v4 v6
AS269956 269956 1 11
v4 v6

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.