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.
83.239.47.0/24 ·
Problem: 83.239.47.0/24 is announced by AS44467 (IRN-STC-AS). 1 problem · 2 warnings
| Announced as | 83.239.47.0/24 |
|---|---|
| Origin AS | AS44467 IRN-STC-AS |
| Holder | ROSTELECOM-MNT |
| Allocation | RIPE NCC, Russia (RU), allocated 2004-02-25 |
| Size | 256 addresses |
| Abuse contact | abuse@rt.ru |
What to fix
-
Problem
83.239.47.0/24 from AS44467 is RPKI invalid: no ROA authorises this origin.
ROAs for this space name AS12389, AS25490. Networks that filter will drop the route – the usual cause of an outage after moving to a new provider or adding DDoS protection.
Fix: Create a ROA for AS44467 (keep the old one until the move is finished), or stop announcing the route from this AS.
prefix: 83.239.47.0/24 origin: AS44467 max-length: 24
-
Warning
No IRR route object for 83.239.47.0/24 with origin AS44467.
Many networks build their prefix filters from IRR data; without a route object some of them drop the route.
Fix: Create a route object in your RIR’s IRR database (or RADB):
route: 83.239.47.0/24 origin: AS44467
-
Warning
Seen by only 8% of RIPE RIS peers.
Partial visibility points to filtering, a missing IRR route object, or an RPKI problem.
Checks
Routing and RPKI 83.239.47.0/24 from AS44467 is RPKI invalid: no ROA authorises this origin.
- Pass: Announced as 83.239.47.0/24 by AS44467.
- Problem: 83.239.47.0/24 from AS44467 is RPKI invalid: no ROA authorises this origin.
- Warning: No IRR route object for 83.239.47.0/24 with origin AS44467.
- Warning: Seen by only 8% of RIPE RIS peers.
| Route | 83.239.47.0/24 |
|---|---|
| Origin AS | AS44467 IRN-STC-AS PJSC Rostelecom RPKI invalid |
| Visibility (RIS peers) | 26 / 319 |
| First seen | 2024-11-06 |
| Covering prefixes | 83.239.32.0/19, 83.239.0.0/18, 83.239.0.0/16 |
| ROA prefix | Max length | Origin AS |
|---|---|---|
| 83.239.47.0/24 | /24 | AS12389 |
| 83.239.32.0/19 | /19 | AS25490 |
| 83.239.0.0/18 | /18 | AS25490 |
| 83.239.0.0/16 | /16 | AS12389 |
Source: RIPEstat (RIPE NCC RIS, Routinator)
Open in ASN & BGP prefix lookupReverse DNS Reverse DNS is delegated (47.239.83.in-addr.arpa).
- Pass: Reverse DNS is delegated (47.239.83.in-addr.arpa).
| Zone | Nameservers |
|---|---|
| 47.239.83.in-addr.arpa | ns.krdn.ru, ns.kuban.ru |
Registration Found at rdap.db.ripe.net.
- Pass: Found at rdap.db.ripe.net.
| Name | Macroregional_South |
|---|---|
| Handle | 83.239.32.0 - 83.239.63.255 |
| Range | 83.239.32.0 – 83.239.63.255 |
| Country | RU |
| Status | active |
| Registered | 2005-02-04T15:19:12Z |
| Last changed | 2024-12-10T10:29:42Z |
| Abuse contact | abuse@rt.ru |
| Registry (RIR) | RIPE NCC |
|---|---|
| Country | Russia (RU) |
| Delegated on | 2004-02-25 |
| Status | Allocated |
| Delegated range | 83.239.0.0/16 (83.239.0.0 – 83.239.255.255) |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| registrant | ROSTELECOM-MNT | |
| abuse | PJSC Rostelecom Technical Team | abuse@rt.ru |
Source: https://rdap.db.ripe.net/ip/83.239.47.0/24. 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
About the network that announces this space, so not in the fix list.
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup