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: AS199408 (BOL-COM bol.com BV) announces 5 IPv4 and 1 IPv6 prefixes. 3 warnings
| AS page | AS199408 |
|---|---|
| Holder | BOL-COM bol.com BV |
| Allocation | RIPE NCC, Netherlands (NL), allocated 2013-01-31 |
| Prefixes (IPv4 / IPv6) | 5 / 1 |
| RPKI valid | 100% (6 / 6) |
| Upstreams and peers | 4 |
| Peering policy | Selective |
What to fix
-
Warning
2 of 6 announced prefixes have no IRR route object: 91.194.15.0/24, 91.194.14.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 AS199408 in your RIR’s IRR database (or RADB).
route: 91.194.15.0/24 origin: AS199408 route: 91.194.14.0/24 origin: AS199408
-
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 2 of 6 announced prefixes have no IRR route object: 91.194.15.0/24, 91.194.14.0/24.
- Pass: AS199408 announces 5 IPv4 and 1 IPv6 prefixes.
- Pass: All 6 announced prefixes are RPKI valid.
- Warning: 2 of 6 announced prefixes have no IRR route object: 91.194.15.0/24, 91.194.14.0/24.
- Info: 4 upstreams and peers, 0 downstream networks seen.
| Holder | BOL-COM bol.com BV |
|---|---|
| IPv4 prefixes | 5 |
| IPv6 prefixes | 1 |
| RPKI | 6 valid |
| Without IRR route object | 2 |
| Downstream networks | 0 |
Upstreams and peers seen to the left 4
Announced prefixes 6
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 | BOL-COM |
|---|---|
| Handle | AS199408 |
| Range | AS199408 |
| Status | active |
| Registered | 2013-01-31T13:48:19Z |
| Last changed | 2026-06-29T10:53:26Z |
| Abuse contact | abuse@bol.com |
| Registry (RIR) | RIPE NCC |
|---|---|
| Country | Netherlands (NL) |
| Delegated on | 2013-01-31 |
| Status | Allocated |
| Delegated range | AS199408 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| registrant | BTIM1-MNT | |
| registrant | bol.com BV | |
| registrant | RIPE-NCC-END-MNT | |
| abuse | Bol.com Technical Infrastructure Management | abuse@bol.com |
Source: https://rdap.db.ripe.net/autnum/199408. 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: AS199408 is in PeeringDB as BOL-COM.
- Info: Peering policy: Selective.
- Info: Present at 3 internet exchanges with 6 ports (60G in total).
- Warning: No IRR as-set is listed.
- Warning: No public NOC, policy or technical contact.
| Network | BOL-COM |
|---|---|
| AS number | AS199408 |
| Type | , Not Disclosed |
| Website | https://www.bol.com |
| Prefixes (IPv4 / IPv6) | 5 / 1 |
| Traffic | Not Disclosed |
| Peering policy | Selective |
| Locations | Not Required |
| Ratio required | No |
| Contracts | Not Required |
| Last updated | 2026-03-25 |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup