bgpreport

Network · data from 2026-11-12

AS19355 SMRN-NET - San Mateo Regional Network, Inc.

Registry name: SMRN-NET - San Mateo Regional Network, Inc., US · not in PeeringDB

8IPv4 routes 0.0% RPKI valid · 100.0% with a route object
2IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
10No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS19355, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS19355, 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.

198.180.184.0/24 No ROA RIR databaseALTDB, ARIN 671 100% 68
199.181.122.0/23 No ROA RIR databaseALTDB, ARIN 671 100% 68
209.234.96.0/20 No ROA RIR databaseALTDB, ARIN, BBOI 671 100% 68
209.234.97.0/24 No ROA RIR databaseARIN 670 100% 68
209.234.99.0/24 No ROA RIR databaseARIN 670 100% 68
209.234.101.0/24 No ROA RIR databaseARIN 670 100% 68
209.234.102.0/24 No ROA RIR databaseARIN 670 100% 68
209.234.110.0/24 No ROA RIR databaseARIN 670 100% 68
2607:ffa0::/32 No ROA RIR databaseARIN 635 100% 70
2607:ffa0:1::/48 No ROA RIR databaseARIN 634 100% 69

AS-SET

AS19355 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 11 are in fix.csv.

  • ROA: none10
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none198.180.184.0/24No ROA covers it. Add a ROA for AS19355, maxLength 24.671 of 673
ROA: none199.181.122.0/23No ROA covers it. Add a ROA for AS19355, maxLength 23.671 of 673
ROA: none209.234.96.0/20No ROA covers it. Add a ROA for AS19355, maxLength 20.671 of 673
ROA: none209.234.97.0/24No ROA covers it. Add a ROA for AS19355, maxLength 24.670 of 673
ROA: none209.234.99.0/24No ROA covers it. Add a ROA for AS19355, maxLength 24.670 of 673
ROA: none209.234.101.0/24No ROA covers it. Add a ROA for AS19355, maxLength 24.670 of 673
ROA: none209.234.102.0/24No ROA covers it. Add a ROA for AS19355, maxLength 24.670 of 673
ROA: none209.234.110.0/24No ROA covers it. Add a ROA for AS19355, maxLength 24.670 of 673
ROA: none2607:ffa0::/32No ROA covers it. Add a ROA for AS19355, maxLength 32.635 of 636
ROA: none2607:ffa0:1::/48No ROA covers it. Add a ROA for AS19355, maxLength 48.634 of 636

Route objects not announced

Route objects with origin AS19355 whose prefix no peer sees AS19355 announce. Many are kept on purpose (backup routes, space announced only in some places).

204.58.180.0/22BBOINo ROA

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.