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

AS48964 ·

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

Warning: AS48964 (ENTERRA-as Private Enterprise "Enterra") announces 17 IPv4 and 0 IPv6 prefixes. 3 warnings

AS pageAS48964
HolderENTERRA-as Private Enterprise "Enterra"
AllocationRIPE NCC, Ukraine (UA), allocated 2009-03-12
Prefixes (IPv4 / IPv6)17 / 0
RPKI valid88% (15 / 17)
Upstreams and peers26
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 17 announced prefixes have no ROA (RPKI not found): 91.227.150.0/23, 141.105.138.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 AS48964 and a max length equal to the prefix length:

    91.227.150.0/23 AS48964 max-length /23
    141.105.138.0/24 AS48964 max-length /24

    Open in RPKI / ROA validator Guide

  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: AS48964 announces 17 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 2 of 17 announced prefixes have no ROA (RPKI not found): 91.227.150.0/23, 141.105.138.0/24.
  • Info: 15 of 17 announced prefixes are RPKI valid.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 26 upstreams and peers, 16 downstream networks seen.
HolderENTERRA-as Private Enterprise "Enterra"
IPv4 prefixes17
IPv6 prefixes0
RPKI15 valid · 2 not found
Downstream networks16
Routes to fix
PrefixRPKI
91.227.150.0/23 No ROA
141.105.138.0/24 No ROA

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.
NameENTERRA-as
HandleAS48964
RangeAS48964
Statusactive
Registered2009-03-12T11:36:46Z
Last changed2026-10-26T07:18:34Z
Abuse contactabuse@datasfera.com
Allocation
Registry (RIR)RIPE NCC
CountryUkraine (UA)
Delegated on2009-03-12
StatusAllocated
Delegated rangeAS48964

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

Contacts
RoleNameEmail
registrant ENTERRAUA-MNT
registrant Private Enterprise "Enterra"
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role abuse@datasfera.com

Source: https://rdap.db.ripe.net/autnum/48964. 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: AS48964 is in PeeringDB as Enterra.
  • Info: Peering policy: Open.
  • Info: Present at 3 internet exchanges with 3 ports (240G in total).
  • Warning: No public NOC, policy or technical contact.
NetworkEnterra
AS numberAS48964
TypeNSP, Regional
Websitehttp://enterra.dp.ua
IRR as-setAS-ENTERRA
Prefixes (IPv4 / IPv6)250 / 0
Traffic500-1000Gbps, Balanced
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2024-12-24

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup