bgpreport

Network · data from 2026-11-12

AS399166 SECURITYSERVICES - Vercara, LLC

Registry name: SECURITYSERVICES - Vercara, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS399166, 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.
204.74.106.0/23 Valid Other IRR onlyRADB 21 3%low visibility 14
204.74.120.0/23 Valid Other IRR onlyRADB 21 3%low visibility 14
156.154.94.0/23 Valid Other IRR onlyRADB 17 3%low visibility 12
156.154.150.0/23 Valid Other IRR onlyRADB 17 3%low visibility 12
204.74.104.0/23 Valid Other IRR onlyRADB 17 3%low visibility 12
2610:a1:3100::/40 Valid Other IRR onlyRADB 6 1%low visibility 4
2610:a1:3200::/40 Valid Other IRR onlyRADB 6 1%low visibility 4

AS-SET

AS399166 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 10 are in fix.csv.

  • Route object: RIR7
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: RIR204.74.106.0/23Route object only in RADB. Add it in the RIR database for the space.21 of 673
Route object: RIR204.74.120.0/23Route object only in RADB. Add it in the RIR database for the space.21 of 673
Route object: RIR156.154.94.0/23Route object only in RADB. Add it in the RIR database for the space.17 of 673
Route object: RIR156.154.150.0/23Route object only in RADB. Add it in the RIR database for the space.17 of 673
Route object: RIR204.74.104.0/23Route object only in RADB. Add it in the RIR database for the space.17 of 673
Route object: RIR2610:a1:3100::/40Route object only in RADB. Add it in the RIR database for the space.6 of 636
Route object: RIR2610:a1:3200::/40Route object only in RADB. Add it in the RIR database for the space.6 of 636

Route objects not announced

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

156.154.94.0/24RADBValid
156.154.95.0/24RADBValid
204.74.104.0/22RADBNo 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.