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

AS30176 ·

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

Warning: AS30176 (AS-PRIORITYCOLO) announces 6 IPv4 and 2 IPv6 prefixes. 3 warnings

AS pageAS30176
HolderAS-PRIORITYCOLO - Priority Colo Inc
AllocationARIN, Canada (CA), assigned 2003-08-04
Prefixes (IPv4 / IPv6)6 / 2
RPKI valid75% (6 / 8)
Upstreams and peers7
Peering policyOpen

What to fix

  1. Warning

    2 of 8 announced prefixes have no ROA (RPKI not found): 206.130.11.0/24, 2607:f698::/31.

    Without a ROA, networks cannot tell your routes from a hijack.

    Fix: Create a ROA for each at your RIR portal, with origin AS30176 and a max length equal to the prefix length:

    206.130.11.0/24 AS30176 max-length /24
    2607:f698::/31 AS30176 max-length /31

    Open in RPKI / ROA validator Guide

  2. Warning

    1 of 8 announced prefixes have no IRR route object: 206.130.11.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 AS30176 in your RIR’s IRR database (or RADB).

    route: 206.130.11.0/24
    origin: AS30176

    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 2 of 8 announced prefixes have no ROA (RPKI not found): 206.130.11.0/24, 2607:f698::/31.
  • Pass: AS30176 announces 6 IPv4 and 2 IPv6 prefixes.
  • Warning: 2 of 8 announced prefixes have no ROA (RPKI not found): 206.130.11.0/24, 2607:f698::/31.
  • Info: 6 of 8 announced prefixes are RPKI valid.
  • Warning: 1 of 8 announced prefixes have no IRR route object: 206.130.11.0/24.
  • Info: 7 upstreams and peers, 6 downstream networks seen.
HolderAS-PRIORITYCOLO - Priority Colo Inc
IPv4 prefixes6
IPv6 prefixes2
RPKI6 valid · 2 not found
Without IRR route object1
Downstream networks6
Routes to fix
PrefixRPKI
206.130.11.0/24 No ROA
2607:f698::/31 No ROA

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.
NameAS-PRIORITYCOLO
HandleAS30176
RangeAS30176
Statusactive
Registered2003-08-04T18:46:14-04:00
Last changed2012-02-24T09:44:34-05:00
Abuse contactabuse@prioritycolo.com
Allocation
Registry (RIR)ARIN
CountryCanada (CA)
Delegated on2003-08-04
StatusAssigned
Delegated rangeAS30176

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

Contacts
RoleNameEmail
registrant Priority Colo Inc
technical Myles M Loosley-Millman ipadmin@prioritycolo.com

Source: https://rdap.arin.net/registry/autnum/30176. 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: AS30176 is in PeeringDB as Priority Colo AS30176.
  • Info: Peering policy: Open.
  • Info: Present at 1 internet exchanges with 1 ports (100G in total).
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2024-05-22.
NetworkPriority Colo AS30176 (PCOLO)
AS numberAS30176
TypeContent, North America
Websitehttp://www.prioritycolo.com
IRR as-setAS30176
Prefixes (IPv4 / IPv6)225 / 40
Traffic5-10Gbps, Mostly Outbound
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2024-05-22

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup