bgpreport

Network · data from 2026-11-12

AS33293 BROADVOICE-LAX - SYNDEO LLC

Registry name: BROADVOICE-LAX - SYNDEO LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS33293, 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.
216.126.204.0/23 No ROA None 673 100% 67
192.81.116.0/22 Valid RIR databaseARIN, RADB 673 100% 67
206.15.152.0/22 Valid RIR databaseARIN 673 100% 67
206.15.156.0/22 Valid RIR databaseARIN 673 100% 67
206.15.150.0/23 Valid RIR databaseARIN 672 100% 67
206.15.162.0/23 Valid RIR databaseARIN 672 100% 67
206.15.164.0/23 Valid RIR databaseARIN 672 100% 67
206.15.174.0/23 Valid RIR databaseARIN 672 100% 67
216.126.204.0/24 Valid RIR databaseARIN 671 100% 67

AS-SET

AS33293 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 5 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none216.126.204.0/23No ROA covers it. Add a ROA for AS33293, maxLength 23.673 of 673
Route object: none216.126.204.0/23No route object for it. Add a route object with origin AS33293 in the RIR database for the space.673 of 673

Route objects not announced

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

206.15.136.0/23ARINValid
206.15.170.0/24RADBNo ROA
208.65.248.0/24RADBNo 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.