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

AS38928 · 

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

Warning: AS38928 (GLONASS JSC GLONASS) announces 4 IPv4 and 0 IPv6 prefixes. 3 warnings

AS pageAS38928
HolderGLONASS JSC GLONASS
AllocationRIPE NCC, Russia (RU), allocated 2015-03-12
Prefixes (IPv4 / IPv6)4 / 0
RPKI valid0% (0 / 4)
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

    4 of 4 announced prefixes have no ROA (RPKI not found): 62.76.137.0/24, 62.76.138.0/24, 193.232.47.0/24, 193.232.77.0/24.

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

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

    62.76.137.0/24 AS38928 max-length /24
62.76.138.0/24 AS38928 max-length /24
193.232.47.0/24 AS38928 max-length /24
193.232.77.0/24 AS38928 max-length /24

    Open in RPKI / ROA validator Guide

  3. 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: AS38928 announces 4 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 4 of 4 announced prefixes have no ROA (RPKI not found): 62.76.137.0/24, 62.76.138.0/24, 193.232.47.0/24, 193.232.77.0/24.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 2 upstreams and peers, 0 downstream networks seen.
HolderGLONASS JSC GLONASS
IPv4 prefixes4
IPv6 prefixes0
RPKI4 not found
Downstream networks0
Routes to fix
PrefixRPKI
62.76.137.0/24 No ROA
62.76.138.0/24 No ROA
193.232.47.0/24 No ROA
193.232.77.0/24 No ROA

Upstreams and peers seen to the left 2

AS3216 VimpelCom AS8359 Mobile TeleSystems PJSC

Announced prefixes 4

62.76.137.0/24 62.76.138.0/24 193.232.47.0/24 193.232.77.0/24

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.
NameGLONASS
HandleAS38928
RangeAS38928
Statusactive
Registered2015-03-12T12:11:49Z
Last changed2022-12-14T08:48:36Z
Abuse contactivm@aoglonass.ru
Allocation
Registry (RIR)RIPE NCC
CountryRussia (RU)
Delegated on2015-03-12
StatusAllocated
Delegated rangeAS38928

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

Contacts
RoleNameEmail
registrant NP-GLONASS-MNT
registrant JSC GLONASS
registrant RIPE-NCC-END-MNT
abuse JSC GLONASS abuse-c Role ivm@aoglonass.ru

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