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

AS3258 ·

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

Warning: AS3258 (XTOM-JAPAN) announces 136 IPv4 and 27 IPv6 prefixes. 1 warning

AS pageAS3258
HolderXTOM-JAPAN xTom Japan Corporation
AllocationRIPE NCC, Japan (JP), allocated 2011-06-17
Prefixes (IPv4 / IPv6)136 / 27
RPKI valid100% (163 / 163)
Upstreams and peers11
Peering policySelective

What to fix

  1. Warning

    1 of 163 announced prefixes have no IRR route object: 2a12:a303:104::/48.

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

    route6: 2a12:a303:104::/48
    origin: AS3258

    Open in ASN & BGP prefix lookup

Checks

Routing and RPKI 1 of 163 announced prefixes have no IRR route object: 2a12:a303:104::/48.
  • Pass: AS3258 announces 136 IPv4 and 27 IPv6 prefixes.
  • Pass: All 163 announced prefixes are RPKI valid.
  • Warning: 1 of 163 announced prefixes have no IRR route object: 2a12:a303:104::/48.
  • Info: 11 upstreams and peers, 6 downstream networks seen.
HolderXTOM-JAPAN xTom Japan Corporation
IPv4 prefixes136
IPv6 prefixes27
RPKI163 valid
Without IRR route object1
Downstream networks6

Announced prefixes 163

5.253.17.0/24 36.50.84.0/23 43.239.249.0/24 45.8.112.0/24 45.8.113.0/24 45.8.114.0/24 45.8.222.0/24 45.11.44.0/24 45.11.46.0/24 45.12.89.0/24 45.14.64.0/24 45.14.65.0/24 45.14.66.0/24 45.14.67.0/24 45.66.129.0/24 45.66.130.0/24 45.66.131.0/24 45.66.216.0/24 45.66.217.0/24 45.66.218.0/24 45.89.232.0/24 45.89.234.0/24 45.89.235.0/24 45.92.159.0/24 45.94.40.0/24 45.128.208.0/24 45.128.209.0/24 45.128.210.0/24 45.128.211.0/24 45.129.8.0/24 45.129.9.0/24 45.129.10.0/24 45.129.11.0/24 45.134.170.0/24 45.134.171.0/24 45.142.125.0/24 45.142.126.0/24 45.142.127.0/24 45.142.166.0/24 45.142.167.0/24 45.143.131.0/24 45.143.232.0/24 45.143.233.0/24 45.143.234.0/24 45.143.235.0/24 45.149.156.0/24 45.149.157.0/24 45.149.158.0/24 45.149.159.0/24 45.153.244.0/24 45.153.245.0/24 45.153.246.0/24 45.153.247.0/24 45.159.48.0/24 45.159.49.0/24 45.159.50.0/24 45.159.51.0/24 62.106.70.0/24 62.106.75.0/24 79.110.232.0/24 85.113.70.0/24 88.214.22.0/24 91.199.209.0/24 91.200.240.0/24 91.200.242.0/24 91.200.243.0/24 92.60.43.0/24 94.124.117.0/24 94.124.118.0/24 95.214.166.0/24 95.214.167.0/24 103.19.1.0/24 103.47.186.0/24 103.53.80.0/23 103.121.208.0/24 103.121.209.0/24 103.121.210.0/24 103.121.211.0/24 103.125.234.0/24 103.125.235.0/24 103.150.8.0/24 103.155.232.0/24 103.155.233.0/24 103.193.129.0/24 103.193.130.0/24 103.201.128.0/24 103.201.130.0/24 103.201.131.0/24 109.107.137.0/24 109.107.140.0/24 109.121.61.0/24 109.121.62.0/24 141.98.196.0/24 141.98.197.0/24 141.98.198.0/24 146.19.19.0/24 146.19.163.0/24 147.78.242.0/24 147.78.243.0/24 147.78.244.0/24

Showing the first 100.

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup
Registration The registry is limiting how often it can be asked. Please try again in a minute.
PeeringDB AS3258 is in PeeringDB as xTom Tokyo.
  • Pass: AS3258 is in PeeringDB as xTom Tokyo.
  • Info: Peering policy: Selective.
  • Info: Present at 3 internet exchanges with 3 ports (300G in total).
NetworkxTom Tokyo (xTom)
AS numberAS3258
TypeCable/DSL/ISP, Asia Pacific
Websitehttps://xtom.com/
IRR as-setRADB::AS-XTOM
Prefixes (IPv4 / IPv6)1000 / 1000
Traffic1-5Tbps, Balanced
Peering policySelective
Policy URLhttps://peering.xtom.com/
LocationsPreferred
Ratio requiredNo
ContractsNot Required
Looking glasshttps://xtom.com/looking-glass/
Last updated2026-11-02
Contacts
Abuseabuse@xtom.com
NOCnoc@xtom.com
Policypeering@xtom.com
Salessales@xtom.com
Technicalsupport@xtom.com

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup