AS265591
265591
Autonomous System AS265591 from MX-HMSC17-LACNIC
Registry
Authoritative registration data
- AS number
- 265591
- Name
- 265591
- Organisation
- Autonomous System AS265591 from MX-HMSC17-LACNIC
- Country
- —
- RIR
- LACNIC
- Registered
Source:asn:rdap
retrieved
IPv4 prefixes
11
IPv6 prefixes
14
Total announced
25
Announced prefixes
Observed in BGP by route collectors, not a registry allocation list
matching
| 200.80.80.0/24 | IPv4 | /24 | not checked | |
| 200.80.81.0/24 | IPv4 | /24 | not checked | |
| 200.80.82.0/24 | IPv4 | /24 | not checked | |
| 200.80.84.0/24 | IPv4 | /24 | not checked | |
| 200.80.85.0/24 | IPv4 | /24 | not checked | |
| 200.80.86.0/24 | IPv4 | /24 | not checked | |
| 200.80.87.0/24 | IPv4 | /24 | not checked | |
| 45.178.88.0/24 | IPv4 | /24 | not checked | |
| 45.178.89.0/24 | IPv4 | /24 | not checked | |
| 45.178.90.0/24 | IPv4 | /24 | not checked | |
| 45.178.91.0/24 | IPv4 | /24 | not checked | |
| 2806:342:e400::/38 | IPv6 | /38 | not checked | |
| 2806:342:e000::/40 | IPv6 | /40 | not checked | |
| 2806:342:e100::/40 | IPv6 | /40 | not checked | |
| 2806:342:e200::/40 | IPv6 | /40 | not checked | |
| 2806:342:e300::/40 | IPv6 | /40 | not checked | |
| 2806:342:f600::/40 | IPv6 | /40 | not checked | |
| 2806:342:f700::/40 | IPv6 | /40 | not checked | |
| 2806:342:f800::/40 | IPv6 | /40 | not checked | |
| 2806:342:fa00::/40 | IPv6 | /40 | not checked | |
| 2806:342:fb00::/40 | IPv6 | /40 | not checked | |
| 2806:342:fc00::/40 | IPv6 | /40 | not checked | |
| 2806:342:fd00::/40 | IPv6 | /40 | not checked | |
| 2806:342:fe00::/40 | IPv6 | /40 | not checked | |
| 2806:342:ff00::/40 | IPv6 | /40 | not checked |
No rows match “”.
Showing – of
Source:ripestat:announced-prefixes
observed
Observed adjacencies
Networks seen next to AS265591 in BGP paths by route collectors.
Observed upstreams
1 networks seen before AS265591 in AS paths
Observed downstreams
0 networks seen after AS265591 in AS paths
No downstreams observed
This AS was not seen carrying traffic towards another network.
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.