Skip to main content

AS262253

262253

Autonomous System AS262253 from PE-EMSA9-LACNIC

Registry

Authoritative registration data

AS number
262253
Name
262253
Organisation
Autonomous System AS262253 from PE-EMSA9-LACNIC
Country
—
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

38

IPv6 prefixes

2

Total announced

40

Announced prefixes

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

Prefixes announced by AS262253
181.224.224.0/19 IPv4 /19 not checked
167.250.204.0/22 IPv4 /22 RPKI valid
167.250.204.0/24 IPv4 /24 RPKI valid
167.250.205.0/24 IPv4 /24 not checked
167.250.206.0/24 IPv4 /24 RPKI valid
167.250.207.0/24 IPv4 /24 RPKI valid
181.224.225.0/24 IPv4 /24 RPKI valid
181.224.226.0/24 IPv4 /24 RPKI valid
181.224.227.0/24 IPv4 /24 RPKI valid
181.224.228.0/24 IPv4 /24 RPKI valid
181.224.229.0/24 IPv4 /24 not checked
181.224.231.0/24 IPv4 /24 RPKI valid
181.224.232.0/24 IPv4 /24 RPKI valid
181.224.235.0/24 IPv4 /24 RPKI valid
181.224.236.0/24 IPv4 /24 not checked
181.224.237.0/24 IPv4 /24 RPKI valid
181.224.238.0/24 IPv4 /24 RPKI valid
181.224.239.0/24 IPv4 /24 not checked
181.224.240.0/24 IPv4 /24 not checked
181.224.241.0/24 IPv4 /24 RPKI valid
181.224.242.0/24 IPv4 /24 RPKI valid
181.224.243.0/24 IPv4 /24 not checked
181.224.244.0/24 IPv4 /24 RPKI valid
181.224.245.0/24 IPv4 /24 not checked
181.224.246.0/24 IPv4 /24 RPKI valid
181.224.247.0/24 IPv4 /24 not checked
181.224.248.0/24 IPv4 /24 not checked
181.224.249.0/24 IPv4 /24 RPKI valid
181.224.250.0/24 IPv4 /24 not checked
181.224.251.0/24 IPv4 /24 not checked
181.224.252.0/24 IPv4 /24 RPKI valid
181.224.253.0/24 IPv4 /24 not checked
181.224.254.0/24 IPv4 /24 RPKI valid
181.224.255.0/24 IPv4 /24 not checked
200.1.182.0/24 IPv4 /24 RPKI not found
200.11.63.0/24 IPv4 /24 RPKI valid
209.45.51.0/24 IPv4 /24 not checked
209.45.95.0/24 IPv4 /24 not checked
2803:2500::/32 IPv6 /32 RPKI valid
2803:5940::/32 IPv6 /32 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 AS262253
Address families
PIT - Peru - Lima: Main 100,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 AS262253 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS262253 in AS paths

Observed upstreams
Families
AS6762 SEABONE-NET 5,194 51,780
v4 v6
AS12956 TELXIUS 7,356 41,298
v4 v6
AS6057 6057 4 330
v4 v6

No rows match “”.

Showing – of

Observed downstreams

26 networks seen after AS262253 in AS paths

Observed downstreams
Families
AS271814 271814 662 46,006
v4 v6
AS267749 267749 3,429 10,784
v4 v6
AS274294 274294 492 9,073
v4 v6
AS270716 ASN270716 535 1,698
v4 v6
AS267743 267743 514 1,641
v4
AS273192 273192 604 1,317
v4 v6
AS273959 273959 514 1,317
v4 v6
AS267747 258 1,308
v4
AS273084 273084 502 676
v4 v6
AS273117 273117 355 659
v4 v6
AS267815 267815 259 658
v4
AS271842 271842 498 656
v4 v6
AS273107 273107 450 656
v4 v6
AS272979 272979 492 652
v4 v6
AS266859 266859 197 483
v4 v6
AS274949 274949 253 394
v4 v6
AS274174 274174 258 329
v4
AS265869 265869 256 329
v4
AS272805 272805 244 329
v6
AS272846 272846 254 328
v4
AS271805 271805 247 317
v4
AS274297 274297 216 292
v6
AS3132 3132 75 264
v4
AS272801 272801 32 40
v4
AS274911 274911 19 25
v4
AS266475 ASN266475 3 8
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS263702 263702 2 2
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.