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

AS29838 ·

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

Warning: AS29838 (AMC) announces 118 IPv4 and 19 IPv6 prefixes. 3 warnings

AS pageAS29838
HolderAMC - Atlantic Metro Communications II, Inc.
AllocationARIN, United States (US), assigned 2003-05-14
Prefixes (IPv4 / IPv6)118 / 19
RPKI valid5% (7 / 137)
Upstreams and peers90
Peering policyOpen

What to fix

  1. Warning

    10 of 137 announced prefixes have no ROA (RPKI not found): 38.81.194.0/24, 38.81.195.0/24, 45.43.5.0/24, 45.43.28.0/24, 66.36.233.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 AS29838 and a max length equal to the prefix length:

    38.81.194.0/24 AS29838 max-length /24
    38.81.195.0/24 AS29838 max-length /24
    45.43.5.0/24 AS29838 max-length /24
    45.43.28.0/24 AS29838 max-length /24
    66.36.233.0/24 AS29838 max-length /24
    66.45.105.0/24 AS29838 max-length /24
    66.178.176.0/20 AS29838 max-length /20
    66.231.176.0/20 AS29838 max-length /20
    66.231.176.0/22 AS29838 max-length /22
    66.231.180.0/22 AS29838 max-length /22

    Open in RPKI / ROA validator Guide

  2. Warning

    79 of 137 announced prefixes have no IRR route object: 67.208.88.0/22, 69.169.24.0/21, 38.81.195.0/24, 2607:f108:1800::/40, 205.251.108.0/22 (+74).

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

    route: 67.208.88.0/22
    origin: AS29838
    
    route: 69.169.24.0/21
    origin: AS29838
    
    route: 38.81.195.0/24
    origin: AS29838

    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 137 announced prefixes have no ROA (RPKI not found): 38.81.194.0/24, 38.81.195.0/24, 45.43.5.0/24, 45.43.28.0/24, 66.36.233.0/24 (+5).
  • Pass: AS29838 announces 118 IPv4 and 19 IPv6 prefixes.
  • Warning: 10 of 137 announced prefixes have no ROA (RPKI not found): 38.81.194.0/24, 38.81.195.0/24, 45.43.5.0/24, 45.43.28.0/24, 66.36.233.0/24 (+5).
  • Info: 7 of 137 announced prefixes are RPKI valid.
  • Info: The RPKI state of 120 prefixes was not looked up (no ROA of AS29838 covers them; only the first 10 are checked).
  • Warning: 79 of 137 announced prefixes have no IRR route object: 67.208.88.0/22, 69.169.24.0/21, 38.81.195.0/24, 2607:f108:1800::/40, 205.251.108.0/22 (+74).
  • Info: 90 upstreams and peers, 85 downstream networks seen.
HolderAMC - Atlantic Metro Communications II, Inc.
IPv4 prefixes118
IPv6 prefixes19
RPKI7 valid · 10 not found · 120 not looked up
Without IRR route object79
Downstream networks85
Routes to fix

Announced prefixes 137

38.81.194.0/24 38.81.195.0/24 45.43.5.0/24 45.43.28.0/24 66.36.233.0/24 66.45.105.0/24 66.178.176.0/20 66.231.176.0/20 66.231.176.0/22 66.231.180.0/22 66.231.180.0/24 66.231.183.0/24 66.231.184.0/22 66.231.190.0/23 67.208.64.0/19 67.208.72.0/21 67.208.72.0/23 67.208.74.0/23 67.208.74.0/24 67.208.76.0/22 67.208.76.0/23 67.208.76.0/24 67.208.77.0/24 67.208.79.0/24 67.208.80.0/21 67.208.88.0/22 67.208.90.0/23 69.9.32.0/20 69.9.44.0/24 69.160.240.0/20 69.160.253.0/24 69.169.14.0/23 69.169.22.0/23 69.169.24.0/21 69.169.24.0/22 69.169.32.0/21 69.169.52.0/23 69.169.56.0/21 69.169.56.0/23 69.169.64.0/19 69.169.80.0/22 69.169.80.0/23 69.169.82.0/23 69.169.88.0/21 70.33.160.0/19 70.33.160.0/21 70.33.160.0/22 70.33.164.0/22 70.33.168.0/21 70.33.176.0/21 70.33.184.0/21 74.91.0.0/20 74.91.10.0/23 74.91.14.0/24 104.128.54.0/24 104.128.63.0/24 104.192.100.0/24 104.194.221.0/24 108.60.128.0/19 108.60.129.0/24 108.60.141.0/24 108.60.156.0/24 139.64.142.0/24 142.154.208.0/24 142.248.239.0/24 162.253.64.0/24 162.253.65.0/24 162.254.85.0/24 167.88.121.0/24 173.45.2.0/23 173.45.2.0/24 173.45.3.0/24 173.45.4.0/22 173.45.16.0/22 173.45.20.0/23 173.45.32.0/20 173.45.40.0/21 173.205.176.0/20 174.128.160.0/20 174.128.176.0/23 174.128.180.0/22 174.128.185.0/24 198.67.15.0/24 199.4.235.0/24 199.27.189.0/24 199.91.216.0/24 199.91.218.0/24 199.115.248.0/23 199.188.159.0/24 199.188.228.0/22 204.145.64.0/19 205.251.0.0/17 205.251.0.0/20 205.251.0.0/21 205.251.8.0/23 205.251.12.0/22 205.251.14.0/23 205.251.16.0/21 205.251.24.0/21 205.251.32.0/19

Showing the first 100.

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

Open in ASN & BGP prefix lookup
Registration Found at rdap.arin.net.
  • Pass: Found at rdap.arin.net.
NameAMC
HandleAS29838
RangeAS29838
Statusactive
Registered2003-05-14T17:56:45-04:00
Last changed2019-04-08T14:25:42-04:00
Abuse contactabuse@atlanticmetro.net
Allocation
Registry (RIR)ARIN
CountryUnited States (US)
Delegated on2003-05-14
StatusAssigned
Delegated rangeAS29838

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

Contacts
RoleNameEmail
registrant Atlantic Metro Communications II, Inc.

Source: https://rdap.arin.net/registry/autnum/29838. Registration data from rdap.arin.net, shown under its terms of use (terms): not for marketing or bulk collection.

Open in WHOIS / RDAP lookup
PeeringDB No public NOC, policy or technical contact.
  • Pass: AS29838 is in PeeringDB as Atlantic Metro.
  • Info: Peering policy: Open.
  • Info: Present at 12 internet exchanges with 13 ports (620G in total).
  • Warning: No public NOC, policy or technical contact.
NetworkAtlantic Metro (AMC)
AS numberAS29838
TypeNSP, Global
Websitehttps://365datacenters.com/
IRR as-setAS-AMC
Prefixes (IPv4 / IPv6)10000 / 600
Traffic50-100Gbps, Mostly Outbound
Peering policyOpen
Policy URLhttps://365datacenters.com/bgp-information/
LocationsPreferred
Ratio requiredNo
ContractsNot Required
Last updated2026-04-21

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup