Network · data from 2026-11-12
AS30148 SUCURI-SEC - Sucuri
Registry name: SUCURI-SEC - Sucuri, US · not in PeeringDB
18IPv4 routes
100.0% RPKI valid · 27.8% with a route object
14IPv6 routes
100.0% RPKI valid · 28.6% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
23 with no route object for this origin
2Low visibility
seen by under 10% of full-table peers
4Route objects not announced
registered with origin AS30148, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS30148, 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.
| 66.248.202.0/24 | Valid | None | 673 100% |
| 66.248.203.0/24 | Valid | Other origin only | 673 100% |
| 185.93.228.0/24 | Valid | Other origin only | 673 100% |
| 185.93.230.0/24 | Valid | None | 673 100% |
| 192.88.134.0/24 | Valid | None | 673 100% |
| 192.88.135.0/24 | Valid | None | 673 100% |
| 208.109.0.0/24 | Valid | Nonecovered by 208.109.0.0/22 | 673 100% |
| 208.109.1.0/24 | Valid | Nonecovered by 208.109.0.0/22 | 673 100% |
| 208.109.2.0/24 | Valid | Nonecovered by 208.109.0.0/22 | 673 100% |
| 208.109.3.0/24 | Valid | Nonecovered by 208.109.0.0/22 | 673 100% |
| 208.109.4.0/22 | Valid | Nonecovered by 208.109.0.0/21 | 673 100% |
| 2a02:fe80:12::/48 | Valid | None | 636 100% |
| 2a02:fe80:15::/48 | Valid | None | 636 100% |
| 2a02:fe80:11::/48 | Valid | None | 635 100% |
| 2a02:fe80:13::/48 | Valid | Other origin only | 635 100% |
| 2a02:fe80:14::/48 | Valid | None | 635 100% |
| 2a02:fe80:17::/48 | Valid | None | 635 100% |
| 2a02:fe80:18::/48 | Valid | None | 635 100% |
| 2a02:fe80:19::/48 | Valid | None | 635 100% |
| 2a02:fe80:20::/48 | Valid | None | 635 100% |
| 2a02:fe80:21::/48 | Valid | None | 635 100% |
| 66.248.201.0/24 | Valid | None | 2 0%low visibility |
| 208.109.80.0/24 | Valid | Nonecovered by 208.109.80.0/21 | 2 0%low visibility |
| 192.124.249.0/24 | Valid | Other IRR onlyNTTCOM | 670 100% |
| 2a02:fe80:16::/48 | Valid | Other IRR onlyNTTCOM | 635 100% |
| 2a02:fe80:1010::/48 | Valid | Other IRR onlyNTTCOM | 634 100% |
| 2a02:fe80:2010::/48 | Valid | Other IRR onlyNTTCOM, RADB | 630 99% |
| 72.167.12.0/22 | Valid | RIR databaseARIN | 673 100% |
| 185.93.231.0/24 | Valid | RIR databaseNTTCOM, RIPE | 673 100% |
| 192.161.0.0/24 | Valid | RIR databaseARIN, NTTCOM | 669 99% |
| 193.19.225.0/24 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 2a02:fe81::/45 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS30148 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 31 are in fix.csv.
- Route object: none23
- Route object: RIR4
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 66.248.202.0/24 | No route object for it. Add a route object with origin AS30148 in the RIR database for the space. |
| Route object: none | 66.248.203.0/24 | Route objects for it name AS26496. Add a route object with origin AS30148 in the RIR database for the space. |
| Route object: none | 185.93.228.0/24 | Route objects for it name AS16509. Add a route object with origin AS30148 in the RIR database for the space. |
| Route object: none | 185.93.230.0/24 | No route object for it. Add a route object with origin AS30148 in the RIR database for the space. |
| Route object: none | 192.88.134.0/24 | No route object for it. Add a route object with origin AS30148 in the RIR database for the space. |
| Route object: none | 192.88.135.0/24 | No route object for it. Add a route object with origin AS30148 in the RIR database for the space. |
| Route object: none | 208.109.0.0/24 | No route object for it. A route object for 208.109.0.0/22 with origin AS30148 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30148 in the RIR database for the space. |
| Route object: none | 208.109.1.0/24 | No route object for it. A route object for 208.109.0.0/22 with origin AS30148 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30148 in the RIR database for the space. |
| Route object: none | 208.109.2.0/24 | No route object for it. A route object for 208.109.0.0/22 with origin AS30148 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30148 in the RIR database for the space. |
| Route object: none | 208.109.3.0/24 | No route object for it. A route object for 208.109.0.0/22 with origin AS30148 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30148 in the RIR database for the space. |
| Route object: none | 208.109.4.0/22 | No route object for it. A route object for 208.109.0.0/21 with origin AS30148 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30148 in the RIR database for the space. |
| Route object: none | 2a02:fe80:12::/48 | No route object for it. Add a route object with origin AS30148 in the RIR database for the space. |
| Route object: none | 2a02:fe80:15::/48 | No route object for it. Add a route object with origin AS30148 in the RIR database for the space. |
| Route object: none | 2a02:fe80:11::/48 | No route object for it. Add a route object with origin AS30148 in the RIR database for the space. |
| Route object: none | 2a02:fe80:13::/48 | Route objects for it name AS16509. Add a route object with origin AS30148 in the RIR database for the space. |
| Route object: none | 2a02:fe80:14::/48 | No route object for it. Add a route object with origin AS30148 in the RIR database for the space. |
| Route object: none | 2a02:fe80:17::/48 | No route object for it. Add a route object with origin AS30148 in the RIR database for the space. |
| Route object: none | 2a02:fe80:18::/48 | No route object for it. Add a route object with origin AS30148 in the RIR database for the space. |
| Route object: none | 2a02:fe80:19::/48 | No route object for it. Add a route object with origin AS30148 in the RIR database for the space. |
| Route object: none | 2a02:fe80:20::/48 | No route object for it. Add a route object with origin AS30148 in the RIR database for the space. |
| Route object: none | 2a02:fe80:21::/48 | No route object for it. Add a route object with origin AS30148 in the RIR database for the space. |
| Route object: none | 66.248.201.0/24 | No route object for it. Add a route object with origin AS30148 in the RIR database for the space. |
| Route object: none | 208.109.80.0/24 | No route object for it. A route object for 208.109.80.0/21 with origin AS30148 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30148 in the RIR database for the space. |
| Route object: RIR | 192.124.249.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 2a02:fe80:16::/48 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 2a02:fe80:1010::/48 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 2a02:fe80:2010::/48 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS30148 whose prefix no peer sees AS30148 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 193.19.224.0/22 | NTTCOM | Valid |
| 208.109.0.0/21 | ARIN | Valid |
| 208.109.0.0/22 | ARIN | Valid |
| 208.109.80.0/21 | ARIN | Valid |
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.