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: AS15692 (RAZORBLUE Razorblue Ltd) announces 9 IPv4 and 5 IPv6 prefixes. 1 warning
| AS page | AS15692 |
|---|---|
| Holder | RAZORBLUE Razorblue Ltd |
| Allocation | RIPE NCC, United Kingdom (GB), allocated 2009-07-30 |
| Prefixes (IPv4 / IPv6) | 9 / 5 |
| RPKI valid | 100% (14 / 14) |
| Upstreams and peers | 5 |
| Peering policy | Selective |
What to fix
-
Warning
4 of 14 announced prefixes have no IRR route object: 2a02:f540::/32, 2a02:f542::/32, 2a02:f541::/32, 2a02:f543::/32.
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 AS15692 in your RIR’s IRR database (or RADB).
route6: 2a02:f540::/32 origin: AS15692 route6: 2a02:f542::/32 origin: AS15692 route6: 2a02:f541::/32 origin: AS15692
Checks
Routing and RPKI 4 of 14 announced prefixes have no IRR route object: 2a02:f540::/32, 2a02:f542::/32, 2a02:f541::/32, 2a02:f543::/32.
- Pass: AS15692 announces 9 IPv4 and 5 IPv6 prefixes.
- Pass: All 14 announced prefixes are RPKI valid.
- Warning: 4 of 14 announced prefixes have no IRR route object: 2a02:f540::/32, 2a02:f542::/32, 2a02:f541::/32, 2a02:f543::/32.
- Info: 5 upstreams and peers, 0 downstream networks seen.
| Holder | RAZORBLUE Razorblue Ltd |
|---|---|
| IPv4 prefixes | 9 |
| IPv6 prefixes | 5 |
| RPKI | 14 valid |
| Without IRR route object | 4 |
| Downstream networks | 0 |
Upstreams and peers seen to the left 5
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 | RAZORBLUE |
|---|---|
| Handle | AS15692 |
| Range | AS15692 |
| Status | active |
| Registered | 2009-07-31T13:06:27Z |
| Last changed | 2025-11-26T18:31:27Z |
| Abuse contact | abuse@razorblue.com |
| Registry (RIR) | RIPE NCC |
|---|---|
| Country | United Kingdom (GB) |
| Delegated on | 2009-07-30 |
| Status | Allocated |
| Delegated range | AS15692 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| registrant | Razorblue Ltd | |
| registrant | RAZORBLUE-MNT | |
| registrant | RIPE-NCC-END-MNT | |
| abuse | Razorblue Abuse Handler | abuse@razorblue.com |
Source: https://rdap.db.ripe.net/autnum/15692. 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 AS15692 is in PeeringDB as razorblue.
- Pass: AS15692 is in PeeringDB as razorblue.
- Info: Peering policy: Selective.
- Info: Present at 3 internet exchanges with 3 ports (40G in total).
- Info: The record was last updated 2023-08-09.
| Network | razorblue |
|---|---|
| AS number | AS15692 |
| Type | NSP, Europe |
| Website | http://www.razorblue.com |
| IRR as-set | RIPE::AS-RAZORBLUE |
| Prefixes (IPv4 / IPv6) | 30 / 10 |
| Traffic | 20-50Gbps, Balanced |
| Peering policy | Selective |
| Locations | Preferred |
| Ratio required | No |
| Contracts | Not Required |
| Looking glass | https://lg.razorblue.com/ |
| Last updated | 2023-08-09 |
| Technical | noc@razorblue.com |
|---|---|
| Policy | peering@razorblue.com |
| Abuse | abuse@razorblue.com |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup