Network · data from 2026-11-12
AS218737 SP-NETWORKING-LLC SP NETWORKING, LLC
Registry name: SP-NETWORKING-LLC SP NETWORKING, LLC, US · not in PeeringDB
7IPv4 routes
100.0% RPKI valid · 14.3% with a route object
20IPv6 routes
100.0% RPKI valid · 30.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
20 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS218737, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS218737, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 2a13:edc0:4::/48 | Valid | Other origin only | 631 99% |
| 2a13:edc0:19::/48 | Valid | Other origin onlycovered by 2a13:edc0:10::/44 | 631 99% |
| 2a13:edc0:661::/48 | Valid | Other origin only | 631 99% |
| 216.23.76.0/23 | Valid | Nonecovered by 216.23.76.0/22 | 544 81% |
| 216.23.78.0/23 | Valid | Nonecovered by 216.23.76.0/22 | 544 81% |
| 216.23.76.0/24 | Valid | Nonecovered by 216.23.76.0/22 | 85 13% |
| 216.23.77.0/24 | Valid | Nonecovered by 216.23.76.0/22 | 85 13% |
| 216.23.78.0/24 | Valid | Nonecovered by 216.23.76.0/22 | 85 13% |
| 216.23.79.0/24 | Valid | Nonecovered by 216.23.76.0/22 | 85 13% |
| 2a13:edc0:21::/48 | Valid | Other origin onlycovered by 2a13:edc0:20::/44 | 81 13% |
| 2a13:edc0:22::/48 | Valid | Other origin onlycovered by 2a13:edc0:20::/44 | 81 13% |
| 2a13:edc0:23::/48 | Valid | Other origin onlycovered by 2a13:edc0:20::/44 | 81 13% |
| 2a13:edc0:301::/48 | Valid | Nonecovered by 2a13:edc0:300::/40 | 76 12% |
| 2a13:edc0:302::/48 | Valid | Nonecovered by 2a13:edc0:300::/40 | 76 12% |
| 2a13:edc0:303::/48 | Valid | Nonecovered by 2a13:edc0:300::/40 | 76 12% |
| 2a13:edc0:304::/48 | Valid | Nonecovered by 2a13:edc0:300::/40 | 76 12% |
| 2a13:edc0:305::/48 | Valid | Nonecovered by 2a13:edc0:300::/40 | 76 12% |
| 2a13:edc0:306::/48 | Valid | Nonecovered by 2a13:edc0:300::/40 | 76 12% |
| 2a13:edc0:307::/48 | Valid | Nonecovered by 2a13:edc0:300::/40 | 76 12% |
| 2a13:edc0:400::/48 | Valid | Nonecovered by 2a13:edc0:400::/40 | 76 12% |
| 216.23.76.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 2a13:edc0:10::/44 | Valid | RIR databaseRIPE | 631 99% |
| 2a13:edc0:18::/48 | Valid | RIR databaseRIPE | 631 99% |
| 2a13:edc0:20::/44 | Valid | RIR databaseRIPE | 631 99% |
| 2a13:edc0:300::/40 | Valid | RIR databaseRIPE | 631 99% |
| 2a13:edc0:400::/40 | Valid | RIR databaseRIPE | 550 86% |
| 2a13:edc0:25::/48 | Valid | RIR databaseRIPE | 81 13% |
AS-SET
AS218737 isn't in PeeringDB, where networks name their AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 20 are in fix.csv.
- Route object: none20
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a13:edc0:4::/48 | Route objects for it name AS216211, AS219425. Add a route object with origin AS218737 in the RIR database for the space. |
| Route object: none | 2a13:edc0:19::/48 | Route objects for it name AS216211. A route object for 2a13:edc0:10::/44 with origin AS218737 covers it (filters allowing more-specifics accept it). Add a route object with origin AS218737 in the RIR database for the space. |
| Route object: none | 2a13:edc0:661::/48 | Route objects for it name AS216211. Add a route object with origin AS218737 in the RIR database for the space. |
| Route object: none | 216.23.76.0/23 | No route object for it. A route object for 216.23.76.0/22 with origin AS218737 covers it (filters allowing more-specifics accept it). Add a route object with origin AS218737 in the RIR database for the space. |
| Route object: none | 216.23.78.0/23 | No route object for it. A route object for 216.23.76.0/22 with origin AS218737 covers it (filters allowing more-specifics accept it). Add a route object with origin AS218737 in the RIR database for the space. |
| Route object: none | 216.23.76.0/24 | No route object for it. A route object for 216.23.76.0/22 with origin AS218737 covers it (filters allowing more-specifics accept it). Add a route object with origin AS218737 in the RIR database for the space. |
| Route object: none | 216.23.77.0/24 | No route object for it. A route object for 216.23.76.0/22 with origin AS218737 covers it (filters allowing more-specifics accept it). Add a route object with origin AS218737 in the RIR database for the space. |
| Route object: none | 216.23.78.0/24 | No route object for it. A route object for 216.23.76.0/22 with origin AS218737 covers it (filters allowing more-specifics accept it). Add a route object with origin AS218737 in the RIR database for the space. |
| Route object: none | 216.23.79.0/24 | No route object for it. A route object for 216.23.76.0/22 with origin AS218737 covers it (filters allowing more-specifics accept it). Add a route object with origin AS218737 in the RIR database for the space. |
| Route object: none | 2a13:edc0:21::/48 | Route objects for it name AS216211. A route object for 2a13:edc0:20::/44 with origin AS218737 covers it (filters allowing more-specifics accept it). Add a route object with origin AS218737 in the RIR database for the space. |
| Route object: none | 2a13:edc0:22::/48 | Route objects for it name AS216211. A route object for 2a13:edc0:20::/44 with origin AS218737 covers it (filters allowing more-specifics accept it). Add a route object with origin AS218737 in the RIR database for the space. |
| Route object: none | 2a13:edc0:23::/48 | Route objects for it name AS216211. A route object for 2a13:edc0:20::/44 with origin AS218737 covers it (filters allowing more-specifics accept it). Add a route object with origin AS218737 in the RIR database for the space. |
| Route object: none | 2a13:edc0:301::/48 | No route object for it. A route object for 2a13:edc0:300::/40 with origin AS218737 covers it (filters allowing more-specifics accept it). Add a route object with origin AS218737 in the RIR database for the space. |
| Route object: none | 2a13:edc0:302::/48 | No route object for it. A route object for 2a13:edc0:300::/40 with origin AS218737 covers it (filters allowing more-specifics accept it). Add a route object with origin AS218737 in the RIR database for the space. |
| Route object: none | 2a13:edc0:303::/48 | No route object for it. A route object for 2a13:edc0:300::/40 with origin AS218737 covers it (filters allowing more-specifics accept it). Add a route object with origin AS218737 in the RIR database for the space. |
| Route object: none | 2a13:edc0:304::/48 | No route object for it. A route object for 2a13:edc0:300::/40 with origin AS218737 covers it (filters allowing more-specifics accept it). Add a route object with origin AS218737 in the RIR database for the space. |
| Route object: none | 2a13:edc0:305::/48 | No route object for it. A route object for 2a13:edc0:300::/40 with origin AS218737 covers it (filters allowing more-specifics accept it). Add a route object with origin AS218737 in the RIR database for the space. |
| Route object: none | 2a13:edc0:306::/48 | No route object for it. A route object for 2a13:edc0:300::/40 with origin AS218737 covers it (filters allowing more-specifics accept it). Add a route object with origin AS218737 in the RIR database for the space. |
| Route object: none | 2a13:edc0:307::/48 | No route object for it. A route object for 2a13:edc0:300::/40 with origin AS218737 covers it (filters allowing more-specifics accept it). Add a route object with origin AS218737 in the RIR database for the space. |
| Route object: none | 2a13:edc0:400::/48 | No route object for it. A route object for 2a13:edc0:400::/40 with origin AS218737 covers it (filters allowing more-specifics accept it). Add a route object with origin AS218737 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS218737 is announced.
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.