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: AS12637 (SEEWEB SEEWEB s.r.l.) announces 33 IPv4 and 10 IPv6 prefixes. 1 problem · 1 warning
| AS page | AS12637 |
|---|---|
| Holder | SEEWEB SEEWEB s.r.l. |
| Allocation | RIPE NCC, Italy (IT), allocated 1999-09-07 |
| Prefixes (IPv4 / IPv6) | 33 / 10 |
| RPKI valid | 98% (42 / 43) |
| Upstreams and peers | 63 |
| Peering policy | Open |
What to fix
-
Problem
1 of 43 announced prefixes are RPKI invalid: 193.17.32.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
1 of 43 announced prefixes have no IRR route object: 185.220.244.0/23.
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 AS12637 in your RIR’s IRR database (or RADB).
route: 185.220.244.0/23 origin: AS12637
Checks
Routing and RPKI 1 of 43 announced prefixes are RPKI invalid: 193.17.32.0/24.
- Pass: AS12637 announces 33 IPv4 and 10 IPv6 prefixes.
- Problem: 1 of 43 announced prefixes are RPKI invalid: 193.17.32.0/24.
- Info: 42 of 43 announced prefixes are RPKI valid.
- Warning: 1 of 43 announced prefixes have no IRR route object: 185.220.244.0/23.
- Info: 63 upstreams and peers, 206 downstream networks seen.
| Holder | SEEWEB SEEWEB s.r.l. |
|---|---|
| IPv4 prefixes | 33 |
| IPv6 prefixes | 10 |
| RPKI | 42 valid · 1 invalid |
| Without IRR route object | 1 |
| Downstream networks | 206 |
| Prefix | RPKI |
|---|---|
| 193.17.32.0/24 | RPKI invalid |
Announced prefixes 43
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 | SEEWEB |
|---|---|
| Handle | AS12637 |
| Range | AS12637 |
| Status | active |
| Registered | 2002-09-18T17:28:36Z |
| Last changed | 2019-12-17T11:30:30Z |
| Abuse contact | abuse@seeweb.it |
| Registry (RIR) | RIPE NCC |
|---|---|
| Country | Italy (IT) |
| Delegated on | 1999-09-07 |
| Status | Allocated |
| Delegated range | AS12637 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| registrant | SEEWEB s.r.l. | |
| registrant | RIPE-NCC-END-MNT | |
| registrant | SEEWEB-MNT | |
| abuse | Seeweb Abuse Desk | abuse@seeweb.it |
Source: https://rdap.db.ripe.net/autnum/12637. 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 AS12637 is in PeeringDB as Seeweb.
- Pass: AS12637 is in PeeringDB as Seeweb.
- Info: Peering policy: Open.
- Info: Present at 5 internet exchanges with 5 ports (50G in total).
| Network | Seeweb |
|---|---|
| AS number | AS12637 |
| Type | Content, Regional |
| Website | https://www.seeweb.it/ |
| IRR as-set | RIPE::AS12637:AS-CUSTOMERS |
| Prefixes (IPv4 / IPv6) | 200 / 50 |
| Traffic | 10-20Gbps, Mostly Outbound |
| Peering policy | Open |
| Locations | Not Required |
| Ratio required | No |
| Contracts | Not Required |
| Looking glass | https://www.seeweb.it/data-center/traceroute-diretto |
| Last updated | 2026-11-03 |
| NOC | noc@seeweb.it |
|---|---|
| Abuse | abuse@seeweb.it |
| Sales | info@seeweb.it |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup