Skip to content
thenetworkery

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.

IP address, prefix or AS number

AS31364 ·

curl -s "https://thenetworkery.com/api/v1/network-report?query=AS31364"
JSON Docs

Warning: AS31364 (INTELBI-AS) announces 60 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS31364
HolderINTELBI-AS Joint Stock Company TransTeleCom
AllocationRIPE NCC, Russia (RU), allocated 2004-04-26
Prefixes (IPv4 / IPv6)60 / 0
RPKI valid0% (0 / 60)
Upstreams and peers2

What to fix

  1. 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.

    Open in ASN & BGP prefix lookup

  2. Warning

    10 of 60 announced prefixes have no ROA (RPKI not found): 83.246.128.0/20, 83.246.144.0/20, 83.246.144.0/24, 83.246.145.0/24, 83.246.146.0/24 (+5).

    Without a ROA, networks cannot tell your routes from a hijack.

    Fix: Create a ROA for each at your RIR portal, with origin AS31364 and a max length equal to the prefix length:

    83.246.128.0/20 AS31364 max-length /20
    83.246.144.0/20 AS31364 max-length /20
    83.246.144.0/24 AS31364 max-length /24
    83.246.145.0/24 AS31364 max-length /24
    83.246.146.0/24 AS31364 max-length /24
    83.246.147.0/24 AS31364 max-length /24
    83.246.148.0/24 AS31364 max-length /24
    83.246.149.0/24 AS31364 max-length /24
    83.246.150.0/24 AS31364 max-length /24
    83.246.151.0/24 AS31364 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

    12 of 60 announced prefixes have no IRR route object: 83.246.238.0/24, 83.246.175.0/24, 83.246.232.0/24, 83.246.233.0/24, 83.246.253.0/24 (+7).

    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 AS31364 in your RIR’s IRR database (or RADB).

    route: 83.246.238.0/24
    origin: AS31364
    
    route: 83.246.175.0/24
    origin: AS31364
    
    route: 83.246.232.0/24
    origin: AS31364

    Open in ASN & BGP prefix lookup

  4. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS31364 announces 60 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 10 of 60 announced prefixes have no ROA (RPKI not found): 83.246.128.0/20, 83.246.144.0/20, 83.246.144.0/24, 83.246.145.0/24, 83.246.146.0/24 (+5).
  • Info: The RPKI state of 50 prefixes was not looked up (no ROA of AS31364 covers them; only the first 10 are checked).
  • Warning: 12 of 60 announced prefixes have no IRR route object: 83.246.238.0/24, 83.246.175.0/24, 83.246.232.0/24, 83.246.233.0/24, 83.246.253.0/24 (+7).
  • Info: 2 upstreams and peers, 1 downstream networks seen.
HolderINTELBI-AS Joint Stock Company TransTeleCom
IPv4 prefixes60
IPv6 prefixes0
RPKI10 not found · 50 not looked up
Without IRR route object12
Downstream networks1
Routes to fix

Upstreams and peers seen to the left 2

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup
Registration Found at rdap.db.ripe.net.
  • Pass: Found at rdap.db.ripe.net.
NameINTELBI-AS
HandleAS31364
RangeAS31364
Statusactive
Registered2004-04-26T12:53:27Z
Last changed2025-01-13T21:16:51Z
Abuse contactabuse@ttk.ru
Allocation
Registry (RIR)RIPE NCC
CountryRussia (RU)
Delegated on2004-04-26
StatusAllocated
Delegated rangeAS31364

Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.

Contacts
RoleNameEmail
registrant Joint Stock Company TransTeleCom
registrant RIPE-NCC-END-MNT
registrant TRANSTELECOM-MNT
abuse TTC NOC abuse@ttk.ru

Source: https://rdap.db.ripe.net/autnum/31364. 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 lookup
PeeringDB 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