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

AS44123 ·

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

Warning: AS44123 (TELAVOX Telavox AB) announces 14 IPv4 and 1 IPv6 prefixes. 3 warnings

AS pageAS44123
HolderTELAVOX Telavox AB
AllocationRIPE NCC, Sweden (SE), allocated 2007-11-20
Prefixes (IPv4 / IPv6)14 / 1
RPKI valid0% (0 / 15)
Upstreams and peers43
Peering policyOpen

What to fix

  1. Warning

    10 of 15 announced prefixes have no ROA (RPKI not found): 80.83.208.0/20, 80.83.212.0/24, 80.83.213.0/24, 80.83.214.0/24, 80.83.215.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 AS44123 and a max length equal to the prefix length:

    80.83.208.0/20 AS44123 max-length /20
    80.83.212.0/24 AS44123 max-length /24
    80.83.213.0/24 AS44123 max-length /24
    80.83.214.0/24 AS44123 max-length /24
    80.83.215.0/24 AS44123 max-length /24
    80.83.216.0/24 AS44123 max-length /24
    80.83.217.0/24 AS44123 max-length /24
    80.83.220.0/24 AS44123 max-length /24
    130.117.193.0/24 AS44123 max-length /24
    130.117.194.0/24 AS44123 max-length /24

    Open in RPKI / ROA validator Guide

  2. Warning

    3 of 15 announced prefixes have no IRR route object: 130.117.204.0/24, 130.117.194.0/24, 130.117.193.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 AS44123 in your RIR’s IRR database (or RADB).

    route: 130.117.204.0/24
    origin: AS44123
    
    route: 130.117.194.0/24
    origin: AS44123
    
    route: 130.117.193.0/24
    origin: AS44123

    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 10 of 15 announced prefixes have no ROA (RPKI not found): 80.83.208.0/20, 80.83.212.0/24, 80.83.213.0/24, 80.83.214.0/24, 80.83.215.0/24 (+5).
  • Pass: AS44123 announces 14 IPv4 and 1 IPv6 prefixes.
  • Warning: 10 of 15 announced prefixes have no ROA (RPKI not found): 80.83.208.0/20, 80.83.212.0/24, 80.83.213.0/24, 80.83.214.0/24, 80.83.215.0/24 (+5).
  • Info: The RPKI state of 5 prefixes was not looked up (no ROA of AS44123 covers them; only the first 10 are checked).
  • Warning: 3 of 15 announced prefixes have no IRR route object: 130.117.204.0/24, 130.117.194.0/24, 130.117.193.0/24.
  • Info: 43 upstreams and peers, 0 downstream networks seen.
HolderTELAVOX Telavox AB
IPv4 prefixes14
IPv6 prefixes1
RPKI10 not found · 5 not looked up
Without IRR route object3
Downstream networks0
Routes to fix

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.
NameTELAVOX
HandleAS44123
RangeAS44123
Statusactive
Registered2007-11-20T16:51:12Z
Last changed2025-06-04T14:27:48Z
Abuse contactoperations@telavox.com
Allocation
Registry (RIR)RIPE NCC
CountrySweden (SE)
Delegated on2007-11-20
StatusAllocated
Delegated rangeAS44123

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

Contacts
RoleNameEmail
registrant MNT-TELAV01
registrant Telavox AB
registrant RIPE-NCC-END-MNT
abuse Telavox Network Operations operations@telavox.com

Source: https://rdap.db.ripe.net/autnum/44123. 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: AS44123 is in PeeringDB as Telavox.
  • Info: Peering policy: Open.
  • Info: Present at 5 internet exchanges with 5 ports (3.2G in total).
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2022-07-27.
NetworkTelavox
AS numberAS44123
TypeContent, Regional
Websitehttp://www.telavox.com
IRR as-setAS-TELAVOX
Prefixes (IPv4 / IPv6)1 / 0
Traffic1-5Gbps, Balanced
Peering policyOpen
LocationsPreferred
Ratio requiredNo
ContractsNot Required
Last updated2022-07-27

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup