AS65534
IPv4 addresses
256
IPv6 /48 networks
1
RPKI
0 valid1 invalid1 no ROA
Peers and downstreams
11
Holder
- AS name
- Organisation
- Not published
- Abuse contact
- Not published
- Registered
- 1995-04-06
- Record last changed
- 2024-05-24 14:19 UTC
Upstream graph
Upstreams and their upstreams, from BGP pathsNetwork health
Grade D · 55/100| fail | Prefixes covered by valid ROAs 0 of 2 announced prefixes are RPKI valid, 1 have no ROA. |
0/25 |
| fail | No RPKI invalid announcements 1 announced prefix is RPKI invalid and dropped by networks that validate. |
0/10 |
| pass | Announces IPv6 1 IPv6 prefix. |
15/15 |
| pass | More than one upstream 3 upstreams seen in BGP. |
10/10 |
| pass | Working abuse contact abuse@iana.org is published. |
15/15 |
| fail | Publishes a geofeed No geofeed found. Without one, location databases have to guess. |
0/10 |
| pass | No prefixes smaller than /24 or /48 All prefixes are /24 (IPv4) or /48 (IPv6) or larger. |
10/10 |
| pass | Registry record maintained Last changed 2024-05-24. |
5/5 |
Routing changes
Last 30 days| 2026-11-19 05:09 UTC | Prefix gone | 195.64.144.0/23 | |
| 2026-11-19 05:09 UTC | Prefix gone | 194.14.46.0/24 | |
| 2026-11-19 05:09 UTC | Prefix gone | 193.235.195.0/24 | |
| 2026-11-19 05:09 UTC | Prefix gone | 193.182.18.0/24 | |
| 2026-11-19 05:09 UTC | Prefix gone | 193.182.170.0/24 | |
| 2026-11-19 05:09 UTC | Prefix gone | 193.182.167.0/24 | |
| 2026-11-19 05:09 UTC | Prefix gone | 193.182.161.0/24 | |
| 2026-11-19 05:09 UTC | Prefix gone | 192.71.45.0/24 | |
| 2026-11-19 05:09 UTC | Prefix gone | 192.176.242.0/24 | |
| 2026-11-19 05:09 UTC | Prefix gone | 192.165.243.0/24 | |
| 2026-11-14 15:42 UTC | New neighbour | AS65193 | peer |
| 2026-11-12 15:17 UTC | New prefix | 2a0f:c380:1::/48 | |
| 2026-11-06 11:27 UTC | Neighbour gone | AS65193 | peer |
| 2026-10-28 05:59 UTC | New neighbour | AS12969 | peer |
WHOIS
aut-num: AS65534 as-name: IANA-RSVD2 handle: AS64512 remarks: These private-use Autonomous System Numbers (ASNs) are set aside for internal use within private networks by the technical documents RFC 1930 and RFC 6996. remarks: remarks: http://tools.ietf.org/html/rfc1930 remarks: http://tools.ietf.org/html/rfc6996 remarks: remarks: If you received this record after looking for the ASN of a BGP peer, you will need to find alternative contact information. Private-use ASNs are not unique, they are not used by any one party, and the party using them may vary depending on your connectivity to the Internet. registrant: IANA (Internet Assigned Numbers Authority) abuse,technical:IANA-IP-ARIN (ICANN) <abuse@iana.org> administrative: IANA-ARIN (Internet Corporation for Assigned Names and Number) <res-ip@iana.org> last changed: 2024-05-24T10:19:53-04:00 registration: 1995-04-06T00:00:00-04:00 source: ARIN (RDAP)