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

AS18986 ·

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

Warning: AS18986 (PACIFICONLINE) announces 45 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS18986
HolderPACIFICONLINE - Calligo (Canada) Inc.
AllocationARIN, Canada (CA), assigned 2000-11-06
Prefixes (IPv4 / IPv6)45 / 0
RPKI valid100% (45 / 45)
Upstreams and peers2
Peering policyOpen

What to fix

  1. Warning

    No IPv6 prefixes announced.

    Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.

    Fix: Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it.

    Open in ASN & BGP prefix lookup

  2. Warning

    2 of 45 announced prefixes have no IRR route object: 173.255.159.0/24, 66.51.171.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 AS18986 in your RIR’s IRR database (or RADB).

    route: 173.255.159.0/24
    origin: AS18986
    
    route: 66.51.171.0/24
    origin: AS18986

    Open in ASN & BGP prefix lookup

  3. Warning

    No IRR as-set is listed.

    Peers and route servers build prefix filters from the as-set. Without one they fall back to the AS number alone, which breaks as soon as you have customers.

    Fix: Create an as-set in your RIR’s IRR database and add it to your PeeringDB record.

    Open in PeeringDB lookup

  4. 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 No IPv6 prefixes announced.
  • Pass: AS18986 announces 45 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Pass: All 45 announced prefixes are RPKI valid.
  • Warning: 2 of 45 announced prefixes have no IRR route object: 173.255.159.0/24, 66.51.171.0/24.
  • Info: 2 upstreams and peers, 0 downstream networks seen.
HolderPACIFICONLINE - Calligo (Canada) Inc.
IPv4 prefixes45
IPv6 prefixes0
RPKI45 valid
Without IRR route object2
Downstream networks0

Upstreams and peers seen to the left 2

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.
NamePACIFICONLINE
HandleAS18986
RangeAS18986
Statusactive
Registered2000-11-06T00:00:00-05:00
Last changed2017-12-08T11:23:48-05:00
Abuse contactrichard.pitman@calligo.io
Allocation
Registry (RIR)ARIN
CountryCanada (CA)
Delegated on2000-11-06
StatusAssigned
Delegated rangeAS18986

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

Contacts
RoleNameEmail
registrant Calligo (Canada) Inc.

Source: https://rdap.arin.net/registry/autnum/18986. 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 IRR as-set is listed.
  • Pass: AS18986 is in PeeringDB as Calligo (Canada).
  • Info: Peering policy: Open.
  • Info: No internet exchange ports are listed.
  • Warning: No IRR as-set is listed.
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2022-07-27.
NetworkCalligo (Canada)
AS numberAS18986
TypeContent, North America
Prefixes (IPv4 / IPv6)16 / 1
Traffic1-5Gbps, Mostly Outbound
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2022-07-27

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup