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

AS210147 ·

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

Warning: AS210147 (am-ispsupport ISP SUPPORT LLC) announces 4 IPv4 and 0 IPv6 prefixes. 3 warnings

AS pageAS210147
Holderam-ispsupport ISP SUPPORT LLC
AllocationRIPE NCC, Armenia (AM), allocated 2018-10-01
Prefixes (IPv4 / IPv6)4 / 0
RPKI valid100% (4 / 4)
Upstreams and peers1
Peering policyOpen

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

    2 of 4 announced prefixes have no IRR route object: 217.113.22.0/24, 217.113.23.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 AS210147 in your RIR’s IRR database (or RADB).

    route: 217.113.22.0/24
    origin: AS210147
    
    route: 217.113.23.0/24
    origin: AS210147

    Open in ASN & BGP prefix lookup

  3. Warning

    No public NOC, policy or technical contact.

    Other networks use these addresses to set up peering and to reach you during an incident.

    Fix: Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public.

    Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS210147 announces 4 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Pass: All 4 announced prefixes are RPKI valid.
  • Warning: 2 of 4 announced prefixes have no IRR route object: 217.113.22.0/24, 217.113.23.0/24.
  • Info: One upstream or peer seen (AS12297): an outage there takes the whole network off the internet.
Holderam-ispsupport ISP SUPPORT LLC
IPv4 prefixes4
IPv6 prefixes0
RPKI4 valid
Without IRR route object2
Downstream networks8

Upstreams and peers seen to the left 1

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.
Nameam-ispsupport
HandleAS210147
RangeAS210147
Statusactive
Registered2018-10-01T13:06:00Z
Last changed2026-03-31T13:20:03Z
Abuse contactabuse@ispsupport.am
Allocation
Registry (RIR)RIPE NCC
CountryArmenia (AM)
Delegated on2018-10-01
StatusAllocated
Delegated rangeAS210147

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

Contacts
RoleNameEmail
registrant lir-am-ispsupport-1-MNT
registrant ISP SUPPORT LLC
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role abuse@ispsupport.am

Source: https://rdap.db.ripe.net/autnum/210147. 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 No public NOC, policy or technical contact.
  • Pass: AS210147 is in PeeringDB as ISP SUPPORT AS210147.
  • Info: Peering policy: Open.
  • Info: No internet exchange ports are listed.
  • Warning: No public NOC, policy or technical contact.
NetworkISP SUPPORT AS210147
AS numberAS210147
TypeNSP, Not Disclosed
Websitehttp://www.ispsupport.am
IRR as-setAS210147:AS-ALL
Prefixes (IPv4 / IPv6)100 / 0
TrafficMostly Inbound
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2025-03-13

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup