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

AS47065 ·

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

Warning: AS47065 (PEERING-RESEARCH-TESTBED-USC-UFMG-AS470…) announces 12 IPv4 and 160 IPv6 prefixes. 2 warnings

AS pageAS47065
HolderPEERING-RESEARCH-TESTBED-USC-UFMG-AS47065 - USC / UFMG PEERING Research Testbed
AllocationARIN, United States (US), assigned 2009-06-16
Prefixes (IPv4 / IPv6)12 / 160
RPKI valid0% (0 / 172)
Upstreams and peers61
Peering policyOpen

What to fix

  1. Warning

    10 of 172 announced prefixes have no ROA (RPKI not found): 138.185.230.0/24, 138.185.231.0/24, 184.164.230.0/24, 184.164.231.0/24, 184.164.237.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 AS47065 and a max length equal to the prefix length:

    138.185.230.0/24 AS47065 max-length /24
    138.185.231.0/24 AS47065 max-length /24
    184.164.230.0/24 AS47065 max-length /24
    184.164.231.0/24 AS47065 max-length /24
    184.164.237.0/24 AS47065 max-length /24
    184.164.239.0/24 AS47065 max-length /24
    184.164.244.0/24 AS47065 max-length /24
    184.164.245.0/24 AS47065 max-length /24
    184.164.250.0/24 AS47065 max-length /24
    184.164.251.0/24 AS47065 max-length /24

    Open in RPKI / ROA validator Guide

  2. 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 172 announced prefixes have no ROA (RPKI not found): 138.185.230.0/24, 138.185.231.0/24, 184.164.230.0/24, 184.164.231.0/24, 184.164.237.0/24 (+5).
  • Pass: AS47065 announces 12 IPv4 and 160 IPv6 prefixes.
  • Warning: 10 of 172 announced prefixes have no ROA (RPKI not found): 138.185.230.0/24, 138.185.231.0/24, 184.164.230.0/24, 184.164.231.0/24, 184.164.237.0/24 (+5).
  • Info: The RPKI state of 162 prefixes was not looked up (no ROA of AS47065 covers them; only the first 10 are checked).
  • Pass: Every announced prefix has an IRR route object.
  • Info: 61 upstreams and peers, 8 downstream networks seen.
HolderPEERING-RESEARCH-TESTBED-USC-UFMG-AS47065 - USC / UFMG PEERING Research Testbed
IPv4 prefixes12
IPv6 prefixes160
RPKI10 not found · 162 not looked up
Downstream networks8

Announced prefixes 172

138.185.230.0/24 138.185.231.0/24 184.164.230.0/24 184.164.231.0/24 184.164.237.0/24 184.164.239.0/24 184.164.244.0/24 184.164.245.0/24 184.164.250.0/24 184.164.251.0/24 184.164.255.0/24 204.9.171.0/24 2804:269c:1::/48 2804:269c:1a::/47 2804:269c:8::/48 2804:269c:10::/48 2804:269c:11::/48 2804:269c:12::/48 2804:269c:13::/48 2804:269c:14::/46 2804:269c:14::/47 2804:269c:14::/48 2804:269c:15::/48 2804:269c:16::/47 2804:269c:17::/48 2804:269c:18::/47 2804:269c:80b9::/48 2804:269c:80bb::/48 2804:269c:80bc::/48 2804:269c:80bd::/48 2804:269c:80c0::/48 2804:269c:80c1::/48 2804:269c:80c3::/48 2804:269c:80c8::/48 2804:269c:80c9::/48 2804:269c:80cb::/48 2804:269c:80cc::/48 2804:269c:80d0::/48 2804:269c:80d1::/48 2804:269c:80d2::/48 2804:269c:80d8::/48 2804:269c:80d9::/48 2804:269c:80da::/48 2804:269c:80db::/48 2804:269c:80e0::/48 2804:269c:80e1::/48 2804:269c:80e2::/48 2804:269c:80e3::/48 2804:269c:80e8::/48 2804:269c:80e9::/48 2804:269c:80ea::/48 2804:269c:80eb::/48 2804:269c:80f1::/48 2804:269c:80f4::/48 2804:269c:80f5::/48 2804:269c:80f9::/48 2804:269c:80fa::/48 2804:269c:80fb::/48 2804:269c:80fc::/48 2804:269c:81a0::/48 2804:269c:81a1::/48 2804:269c:81a2::/48 2804:269c:81a8::/48 2804:269c:81b0::/48 2804:269c:81b1::/48 2804:269c:81ca::/48 2804:269c:81cb::/48 2804:269c:81cc::/48 2804:269c:81cd::/48 2804:269c:81ce::/48 2804:269c:810a::/48 2804:269c:811a::/48 2804:269c:811b::/48 2804:269c:812a::/48 2804:269c:812b::/48 2804:269c:813a::/48 2804:269c:813b::/48 2804:269c:815a::/48 2804:269c:815b::/48 2804:269c:815c::/48 2804:269c:817a::/48 2804:269c:817b::/48 2804:269c:818a::/48 2804:269c:8100::/48 2804:269c:8101::/48 2804:269c:8103::/48 2804:269c:8104::/48 2804:269c:8105::/48 2804:269c:8108::/48 2804:269c:8109::/48 2804:269c:8118::/48 2804:269c:8119::/48 2804:269c:8120::/48 2804:269c:8121::/48 2804:269c:8123::/48 2804:269c:8129::/48 2804:269c:8130::/48 2804:269c:8131::/48 2804:269c:8132::/48 2804:269c:8138::/48

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.
NamePEERING-RESEARCH-TESTBED-USC-UFMG-AS47065
HandleAS47065
RangeAS47065
Statusactive
Registered2009-06-16T18:22:20-04:00
Last changed2019-04-23T14:42:11-04:00
Abuse contactta2510@columbia.edu
Allocation
Registry (RIR)ARIN
CountryUnited States (US)
Delegated on2009-06-16
StatusAssigned
Delegated rangeAS47065

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

Contacts
RoleNameEmail
registrant USC / UFMG PEERING Research Testbed

Source: https://rdap.arin.net/registry/autnum/47065. 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: AS47065 is in PeeringDB as Columbia/UFMG PEERING Research Testbed.
  • Info: Peering policy: Open.
  • Info: Present at 3 internet exchanges with 3 ports (20.1G in total).
  • Warning: No public NOC, policy or technical contact.
NetworkColumbia/UFMG PEERING Research Testbed (Transit Portal, BGPMUX)
AS numberAS47065
TypeEducational/Research, Global
Websitehttp://peering.ee.columbia.edu
IRR as-setRS-PEERING-TESTBED
Prefixes (IPv4 / IPv6)100 / 300
Traffic20-100Mbps, Balanced
Peering policyOpen
Policy URLhttp://peering.ee.columbia.edu/peering/
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2026-06-24

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup