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: AS42610 (NCNET-AS PJSC Rostelecom) announces 32 IPv4 and 2 IPv6 prefixes. 2 warnings
| AS page | AS42610 |
|---|---|
| Holder | NCNET-AS PJSC Rostelecom |
| Allocation | RIPE NCC, Russia (RU), allocated 2007-03-22 |
| Prefixes (IPv4 / IPv6) | 32 / 2 |
| RPKI valid | 94% (32 / 34) |
| Upstreams and peers | 4 |
| Peering policy | Selective |
What to fix
-
Warning
2 of 34 announced prefixes have no ROA (RPKI not found): 87.240.40.0/21, 87.240.48.0/20.
Without a ROA, networks cannot tell your routes from a hijack.
Fix: Create a ROA for each at your RIR portal, with origin AS42610 and a max length equal to the prefix length:
87.240.40.0/21 AS42610 max-length /21 87.240.48.0/20 AS42610 max-length /20
-
Warning
No public NOC, policy or technical contact.
Other networks use these addresses to set up peering and to reach you during an incident.
Fix: Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public.
Checks
Routing and RPKI 2 of 34 announced prefixes have no ROA (RPKI not found): 87.240.40.0/21, 87.240.48.0/20.
- Pass: AS42610 announces 32 IPv4 and 2 IPv6 prefixes.
- Warning: 2 of 34 announced prefixes have no ROA (RPKI not found): 87.240.40.0/21, 87.240.48.0/20.
- Info: 32 of 34 announced prefixes are RPKI valid.
- Pass: Every announced prefix has an IRR route object.
- Info: 4 upstreams and peers, 7 downstream networks seen.
| Holder | NCNET-AS PJSC Rostelecom |
|---|---|
| IPv4 prefixes | 32 |
| IPv6 prefixes | 2 |
| RPKI | 32 valid · 2 not found |
| Downstream networks | 7 |
| Prefix | RPKI |
|---|---|
| 87.240.40.0/21 | No ROA |
| 87.240.48.0/20 | No ROA |
Upstreams and peers seen to the left 4
Announced prefixes 34
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 | NCNET-AS |
|---|---|
| Handle | AS42610 |
| Range | AS42610 |
| Status | active |
| Registered | 2007-03-22T09:50:49Z |
| Last changed | 2026-08-17T09:52:52Z |
| Abuse contact | abuse@rt.ru |
| Registry (RIR) | RIPE NCC |
|---|---|
| Country | Russia (RU) |
| Delegated on | 2007-03-22 |
| Status | Allocated |
| Delegated range | AS42610 |
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/42610. 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 No public NOC, policy or technical contact.
- Pass: AS42610 is in PeeringDB as Rostelecom MRB Moscow.
- Info: Peering policy: Selective.
- Info: No internet exchange ports are listed.
- Warning: No public NOC, policy or technical contact.
- Info: The record was last updated 2022-07-27.
| Network | Rostelecom MRB Moscow (National Cable Networks, "Onlime") |
|---|---|
| AS number | AS42610 |
| Type | Cable/DSL/ISP, Regional |
| Website | http://moscow.rt.ru |
| IRR as-set | AS-NCNET |
| Prefixes (IPv4 / IPv6) | 300 / 15 |
| Traffic | 300-500Gbps, Balanced |
| Peering policy | Selective |
| Locations | Preferred |
| Ratio required | Yes |
| Contracts | Not Required |
| Last updated | 2022-07-27 |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup