Skip to main content

AS263185

263185

Autonomous System AS263185 from PE-MCPS3-LACNIC

Registry

Authoritative registration data

AS number
263185
Name
263185
Organisation
Autonomous System AS263185 from PE-MCPS3-LACNIC
Country
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

14

IPv6 prefixes

1

Total announced

15

Announced prefixes

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

Prefixes announced by AS263185
179.43.80.0/24 IPv4 /24 not checked
179.43.81.0/24 IPv4 /24 not checked
179.43.82.0/24 IPv4 /24 not checked
179.43.83.0/24 IPv4 /24 not checked
179.43.84.0/24 IPv4 /24 not checked
179.43.85.0/24 IPv4 /24 not checked
179.43.86.0/24 IPv4 /24 not checked
179.43.87.0/24 IPv4 /24 not checked
179.43.88.0/24 IPv4 /24 not checked
179.43.89.0/24 IPv4 /24 not checked
179.43.90.0/24 IPv4 /24 not checked
179.43.91.0/24 IPv4 /24 not checked
179.43.93.0/24 IPv4 /24 not checked
179.43.94.0/24 IPv4 /24 not checked
2803:2480::/32 IPv6 /32 not checked

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 AS263185
Address families
PIT - Peru - Arequipa 10,000 Mbps IPv4 · IPv6
PIT - Peru - Lima: Main 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 AS263185 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS263185 in AS paths

Observed upstreams
Families
AS7195 7195 1,454 7,151
v4 v6
AS21575 21575 219 716
v4
AS6057 6057 6 44
v4 v6

No rows match “”.

Showing of

Observed downstreams

3 networks seen after AS263185 in AS paths

Observed downstreams
Families
AS271862 482 1,077
v4 v6
AS272106 387 855
v4 v6
AS265869 275 700
v4

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.