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

AS47656 · 

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

Warning: AS47656 (AST-SYSTEMS-AS) announces 7 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS47656
HolderAST-SYSTEMS-AS Ast-Systems Ltd.
AllocationRIPE NCC, Russia (RU), allocated 2008-07-28
Prefixes (IPv4 / IPv6)7 / 0
RPKI valid0% (0 / 7)
Upstreams and peers3

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

    7 of 7 announced prefixes have no ROA (RPKI not found): 91.206.148.0/23, 91.206.149.0/24, 95.215.148.0/24, 95.215.150.0/23, 95.215.151.0/24 (+2).

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

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

    91.206.148.0/23 AS47656 max-length /23
91.206.149.0/24 AS47656 max-length /24
95.215.148.0/24 AS47656 max-length /24
95.215.150.0/23 AS47656 max-length /23
95.215.151.0/24 AS47656 max-length /24
195.54.40.0/23 AS47656 max-length /23
195.54.41.0/24 AS47656 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

    1 of 7 announced prefixes have no IRR route object: 95.215.150.0/23.

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

    route: 95.215.150.0/23
origin: AS47656

    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: AS47656 announces 7 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 7 of 7 announced prefixes have no ROA (RPKI not found): 91.206.148.0/23, 91.206.149.0/24, 95.215.148.0/24, 95.215.150.0/23, 95.215.151.0/24 (+2).
  • Warning: 1 of 7 announced prefixes have no IRR route object: 95.215.150.0/23.
  • Info: 3 upstreams and peers, 3 downstream networks seen.
HolderAST-SYSTEMS-AS Ast-Systems Ltd.
IPv4 prefixes7
IPv6 prefixes0
RPKI7 not found
Without IRR route object1
Downstream networks3
Routes to fix
PrefixRPKI
91.206.148.0/23 No ROA
91.206.149.0/24 No ROA
95.215.148.0/24 No ROA
95.215.150.0/23 No ROA
95.215.151.0/24 No ROA
195.54.40.0/23 No ROA
195.54.41.0/24 No ROA

Upstreams and peers seen to the left 3

AS20485 TransTelecom AS3216 VimpelCom AS12389 Rostelecom

Announced prefixes 7

91.206.148.0/23 91.206.149.0/24 95.215.148.0/24 95.215.150.0/23 95.215.151.0/24 195.54.40.0/23 195.54.41.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.
NameAST-SYSTEMS-AS
HandleAS47656
RangeAS47656
Statusactive
Registered2008-07-28T13:23:12Z
Last changed2019-04-04T12:16:22Z
Abuse contactpost@astsystems.ru
Allocation
Registry (RIR)RIPE NCC
CountryRussia (RU)
Delegated on2008-07-28
StatusAllocated
Delegated rangeAS47656

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

Contacts
RoleNameEmail
registrant MNT-AST-SYSTEMS
registrant Ast-Systems Ltd.
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role post@astsystems.ru

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