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.
Warning: AS15765 (MIMER Tafjord Connect AS) announces 3 IPv4 and 1 IPv6 prefixes. 2 warnings
| AS page | AS15765 |
|---|---|
| Holder | MIMER Tafjord Connect AS |
| Allocation | RIPE NCC, Norway (NO), allocated 2000-10-06 |
| Prefixes (IPv4 / IPv6) | 3 / 1 |
| RPKI valid | 100% (4 / 4) |
| Upstreams and peers | 1 |
| Peering policy | Open |
What to fix
-
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.
-
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.
Checks
Routing and RPKI AS15765 announces 3 IPv4 and 1 IPv6 prefixes.
- Pass: AS15765 announces 3 IPv4 and 1 IPv6 prefixes.
- Pass: All 4 announced prefixes are RPKI valid.
- Pass: Every announced prefix has an IRR route object.
- Info: One upstream or peer seen (AS25400): an outage there takes the whole network off the internet.
| Holder | MIMER Tafjord Connect AS |
|---|---|
| IPv4 prefixes | 3 |
| IPv6 prefixes | 1 |
| RPKI | 4 valid |
| Downstream networks | 1 |
Upstreams and peers seen to the left 1
Announced prefixes 4
Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru
Open in ASN & BGP prefix lookupRegistration Found at rdap.db.ripe.net.
- Pass: Found at rdap.db.ripe.net.
| Name | MIMER |
|---|---|
| Handle | AS15765 |
| Range | AS15765 |
| Status | active |
| Registered | 2002-02-28T13:18:16Z |
| Last changed | 2024-09-30T09:40:43Z |
| Abuse contact | abuse@notify.tafjordconnect.no |
| Registry (RIR) | RIPE NCC |
|---|---|
| Country | Norway (NO) |
| Delegated on | 2000-10-06 |
| Status | Allocated |
| Delegated range | AS15765 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| registrant | MIMER-MNT | |
| registrant | Tafjord Connect AS | |
| registrant | RIPE-NCC-END-MNT | |
| abuse | Abuse Role | abuse@notify.tafjordconnect.no |
Source: https://rdap.db.ripe.net/autnum/15765. Registration data from rdap.db.ripe.net, shown under its terms of use (terms): not for marketing or bulk collection. Personal contacts in this registry are not shown.
Open in WHOIS / RDAP lookupPeeringDB No IRR as-set is listed.
- Pass: AS15765 is in PeeringDB as Tafjord Marked AS.
- 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.
| Network | Tafjord Marked AS |
|---|---|
| AS number | AS15765 |
| Type | Cable/DSL/ISP, Europe |
| Website | http://tafjord.no |
| Prefixes (IPv4 / IPv6) | 4 / 1 |
| Traffic | 1-5Gbps, Mostly Inbound |
| Peering policy | Open |
| Locations | Not Required |
| Ratio required | No |
| Contracts | Not Required |
| Last updated | 2022-07-27 |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup