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.
Checking routing, RPKI, reverse DNS, blocklists and the registry. This usually takes 3 to 10 seconds.
Problem: AS7861 (TELUS-7861) announces 36 IPv4 and 0 IPv6 prefixes. 1 problem · 3 warnings
| AS page | AS7861 |
|---|---|
| Holder | TELUS-7861 - TELUS Communications Inc. |
| Allocation | ARIN, Canada (CA), assigned 2002-01-02 |
| Prefixes (IPv4 / IPv6) | 36 / 0 |
| RPKI valid | 97% (35 / 36) |
| Upstreams and peers | 1 |
What to fix
-
Problem
1 of 36 announced prefixes are RPKI invalid: 66.203.206.0/24.
A ROA covers them but does not allow this origin or prefix length, so networks that filter (most large ones do) drop these routes.
Fix: Fix the ROAs (origin AS and max length) at your RIR, or stop announcing the routes.
-
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.
-
Warning
2 of 36 announced prefixes have no IRR route object: 66.203.206.0/24, 209.29.245.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 AS7861 in your RIR’s IRR database (or RADB).
route: 66.203.206.0/24 origin: AS7861 route: 209.29.245.0/24 origin: AS7861
- Warning
Checks
Routing and RPKI 1 of 36 announced prefixes are RPKI invalid: 66.203.206.0/24.
- Pass: AS7861 announces 36 IPv4 and 0 IPv6 prefixes.
- Warning: No IPv6 prefixes announced.
- Problem: 1 of 36 announced prefixes are RPKI invalid: 66.203.206.0/24.
- Info: 35 of 36 announced prefixes are RPKI valid.
- Warning: 2 of 36 announced prefixes have no IRR route object: 66.203.206.0/24, 209.29.245.0/24.
- Info: One upstream or peer seen (AS852): an outage there takes the whole network off the internet.
| Holder | TELUS-7861 - TELUS Communications Inc. |
|---|---|
| IPv4 prefixes | 36 |
| IPv6 prefixes | 0 |
| RPKI | 35 valid · 1 invalid |
| Without IRR route object | 2 |
| Downstream networks | 0 |
| Prefix | RPKI |
|---|---|
| 66.203.206.0/24 | RPKI invalid |
Upstreams and peers seen to the left 1
Announced prefixes 36
Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru
Open in ASN & BGP prefix lookupRegistration Found at rdap.arin.net.
- Pass: Found at rdap.arin.net.
| Name | TELUS-7861 |
|---|---|
| Handle | AS7861 |
| Range | AS7861 |
| Status | active |
| Registered | 2002-01-02T00:00:00-05:00 |
| Last changed | 2012-02-24T09:44:34-05:00 |
| Abuse contact | abuse@telus.com |
| Registry (RIR) | ARIN |
|---|---|
| Country | Canada (CA) |
| Delegated on | 2002-01-02 |
| Status | Assigned |
| Delegated range | AS7861 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| registrant | TELUS Communications Inc. | |
| technical | Hostmaster | Hostmaster@telus.com |
Source: https://rdap.arin.net/registry/autnum/7861. Registration data from rdap.arin.net, shown under its terms of use (terms): not for marketing or bulk collection.
Open in WHOIS / RDAP lookupPeeringDB PeeringDB did not answer: HTTP 404
- Warning: PeeringDB did not answer: HTTP 404
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup