Network report
Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.
Checking routing, RPKI, reverse DNS, blocklists and the registry. This usually takes 3 to 10 seconds.
Warning: AS25515 (CTCNET-AS) announces 20 IPv4 and 1 IPv6 prefixes. 2 warnings
| AS page | AS25515 |
|---|---|
| Holder | CTCNET-AS PJSC Rostelecom |
| Allocation | RIPE NCC, Russia (RU), allocated 2002-12-18 |
| Prefixes (IPv4 / IPv6) | 20 / 1 |
| RPKI valid | 100% (21 / 21) |
| Upstreams and peers | 1 |
What to fix
-
Warning
7 of 21 announced prefixes have no IRR route object: 77.51.192.0/21, 77.51.224.0/21, 77.51.176.0/21, 77.51.208.0/21, 77.51.184.0/21 (+2).
Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.
Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS25515 in your RIR’s IRR database (or RADB).
route: 77.51.192.0/21 origin: AS25515 route: 77.51.224.0/21 origin: AS25515 route: 77.51.176.0/21 origin: AS25515
- Warning
Checks
Routing and RPKI 7 of 21 announced prefixes have no IRR route object: 77.51.192.0/21, 77.51.224.0/21, 77.51.176.0/21, 77.51.208.0/21, 77.51.184.0/21 (+2).
- Pass: AS25515 announces 20 IPv4 and 1 IPv6 prefixes.
- Pass: All 21 announced prefixes are RPKI valid.
- Warning: 7 of 21 announced prefixes have no IRR route object: 77.51.192.0/21, 77.51.224.0/21, 77.51.176.0/21, 77.51.208.0/21, 77.51.184.0/21 (+2).
- Info: One upstream or peer seen (AS12389): an outage there takes the whole network off the internet.
| Holder | CTCNET-AS PJSC Rostelecom |
|---|---|
| IPv4 prefixes | 20 |
| IPv6 prefixes | 1 |
| RPKI | 21 valid |
| Without IRR route object | 7 |
| Downstream networks | 4 |
Upstreams and peers seen to the left 1
Announced prefixes 21
Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru
Open in ASN & BGP prefix lookupRegistration Found at rdap.db.ripe.net.
- Pass: Found at rdap.db.ripe.net.
| Name | CTCNET-AS |
|---|---|
| Handle | AS25515 |
| Range | AS25515 |
| Status | active |
| Registered | 2002-12-18T09:00:24Z |
| Last changed | 2026-05-25T07:55:30Z |
| Abuse contact | abuse@rt.ru |
| Registry (RIR) | RIPE NCC |
|---|---|
| Country | Russia (RU) |
| Delegated on | 2002-12-18 |
| Status | Allocated |
| Delegated range | AS25515 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| registrant | PJSC Rostelecom | |
| registrant | RIPE-NCC-END-MNT | |
| registrant | ROSTELECOM-MNT | |
| abuse | PJSC Rostelecom Technical Team | abuse@rt.ru |
Source: https://rdap.db.ripe.net/autnum/25515. Registration data from rdap.db.ripe.net, shown under its terms of use (terms): not for marketing or bulk collection. Personal contacts in this registry are not shown.
Open in WHOIS / RDAP lookupPeeringDB PeeringDB did not answer: HTTP 404
- Warning: PeeringDB did not answer: HTTP 404
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup