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: AS28775 (TTCNET OOO TRANSTELECOM) announces 4 IPv4 and 0 IPv6 prefixes. 4 warnings
| AS page | AS28775 |
|---|---|
| Holder | TTCNET OOO TRANSTELECOM |
| Allocation | RIPE NCC, Russia (RU), allocated 2003-02-20 |
| Prefixes (IPv4 / IPv6) | 4 / 0 |
| RPKI valid | 0% (0 / 4) |
| Upstreams and peers | 3 |
What to fix
-
Warning
No IPv6 prefixes announced.
Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.
Fix: Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it.
-
Warning
4 of 4 announced prefixes have no ROA (RPKI not found): 5.57.232.0/21, 5.57.239.0/24, 94.198.192.0/21, 217.21.208.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 AS28775 and a max length equal to the prefix length:
5.57.232.0/21 AS28775 max-length /21 5.57.239.0/24 AS28775 max-length /24 94.198.192.0/21 AS28775 max-length /21 217.21.208.0/20 AS28775 max-length /20
-
Warning
1 of 4 announced prefixes have no IRR route object: 5.57.239.0/24.
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 AS28775 in your RIR’s IRR database (or RADB).
route: 5.57.239.0/24 origin: AS28775
- Warning
Checks
Routing and RPKI No IPv6 prefixes announced.
- Pass: AS28775 announces 4 IPv4 and 0 IPv6 prefixes.
- Warning: No IPv6 prefixes announced.
- Warning: 4 of 4 announced prefixes have no ROA (RPKI not found): 5.57.232.0/21, 5.57.239.0/24, 94.198.192.0/21, 217.21.208.0/20.
- Warning: 1 of 4 announced prefixes have no IRR route object: 5.57.239.0/24.
- Info: 3 upstreams and peers, 8 downstream networks seen.
| Holder | TTCNET OOO TRANSTELECOM |
|---|---|
| IPv4 prefixes | 4 |
| IPv6 prefixes | 0 |
| RPKI | 4 not found |
| Without IRR route object | 1 |
| Downstream networks | 8 |
| Prefix | RPKI |
|---|---|
| 5.57.232.0/21 | No ROA |
| 5.57.239.0/24 | No ROA |
| 94.198.192.0/21 | No ROA |
| 217.21.208.0/20 | No ROA |
Upstreams and peers seen to the left 3
Announced prefixes 4
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 | TTCNET |
|---|---|
| Handle | AS28775 |
| Range | AS28775 |
| Status | active |
| Registered | 2003-02-20T09:47:30Z |
| Last changed | 2026-06-03T13:10:28Z |
| Abuse contact | abuse@transtelecom.ru |
| Registry (RIR) | RIPE NCC |
|---|---|
| Country | Russia (RU) |
| Delegated on | 2003-02-20 |
| Status | Allocated |
| Delegated range | AS28775 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| registrant | OOO TRANSTELECOM | |
| registrant | RIPE-NCC-END-MNT | |
| registrant | TTCNET-MNT | |
| abuse | OAO TRANSTELECOM NOC | abuse@transtelecom.ru |
Source: https://rdap.db.ripe.net/autnum/28775. 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