bgpreport

Network · data from 2026-11-12

AS210334 Synertech

Registry name: synertech Synertech Network Inc., SC · PeeringDB

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

Announced routes

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

154.89.49.0/24 Valid Other IRR onlyRADB 672 100% 67
175.29.108.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
175.29.109.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
175.29.110.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
175.29.111.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
154.89.47.0/24 Valid RIR databaseAFRINIC, RADB 672 100% 67
154.89.50.0/24 Valid RIR databaseAFRINIC, RADB 672 100% 67
154.89.51.0/24 Valid RIR databaseAFRINIC, RADB 672 100% 67
154.89.52.0/24 Valid RIR databaseAFRINIC, RADB 672 100% 67
154.89.53.0/24 Valid RIR databaseAFRINIC, RADB 672 100% 67
154.89.54.0/24 Valid RIR databaseAFRINIC, RADB 672 100% 67
154.89.56.0/24 Valid RIR databaseAFRINIC, RADB 672 100% 67
154.89.57.0/24 Valid RIR databaseAFRINIC, RADB 672 100% 67
154.89.58.0/24 Valid RIR databaseAFRINIC, RADB 672 100% 67
154.89.59.0/24 Valid RIR databaseAFRINIC, RADB 672 100% 67
154.89.60.0/24 Valid RIR databaseAFRINIC, RADB 672 100% 67
154.89.61.0/24 Valid RIR databaseAFRINIC, RADB 672 100% 67
154.89.62.0/24 Valid RIR databaseAFRINIC, RADB 672 100% 67
154.89.63.0/24 Valid RIR databaseAFRINIC, RADB 672 100% 67
175.29.108.0/22 Valid RIR databaseAPNIC, RADB 672 100% 67
154.89.32.0/19 Valid RIR databaseAFRINIC, RADB 671 100% 67
154.89.32.0/20 Valid RIR databaseAFRINIC, RADB 61 9%low visibility 33
154.89.32.0/22 Valid RIR databaseAFRINIC, RADB 61 9%low visibility 33
154.89.44.0/24 Valid RIR databaseAFRINIC, RADB 12 2%low visibility 12

AS-SET

AS210334's PeeringDB record names no 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 47 are in fix.csv.

  • Route object: RIR1
  • Route object: not announced46
ChangePrefix or setDetailFull-table peers
Route object: RIR154.89.49.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

154.89.32.0/21RADBValid
154.89.32.0/23RADBValid
154.89.32.0/24RADBValid
154.89.33.0/24RADBValid
154.89.34.0/23RADBValid
154.89.34.0/24RADBValid
154.89.35.0/24RADBValid
154.89.36.0/22RADBValid
154.89.36.0/23RADBValid
154.89.36.0/24RADBValid
154.89.37.0/24RADBValid
154.89.38.0/23RADBValid
154.89.38.0/24RADBValid
154.89.39.0/24RADBValid
154.89.40.0/21RADBValid
154.89.40.0/22RADBValid
154.89.40.0/23RADBValid
154.89.40.0/24AFRINIC, RADBValid
154.89.41.0/24RADBValid
154.89.42.0/23RADBValid
154.89.42.0/24RADBValid
154.89.43.0/24RADBValid
154.89.44.0/22RADBValid
154.89.44.0/23RADBValid
154.89.45.0/24RADBValid
154.89.46.0/23RADBValid
154.89.46.0/24AFRINIC, RADBValid
154.89.48.0/20RADBValid
154.89.48.0/21RADBValid
154.89.48.0/22RADBValid
154.89.48.0/23RADBValid
154.89.48.0/24AFRINIC, RADBValid
154.89.50.0/23RADBValid
154.89.52.0/22RADBValid
154.89.52.0/23RADBValid
154.89.54.0/23RADBValid
154.89.55.0/24AFRINIC, RADBValid
154.89.56.0/21RADBValid
154.89.56.0/22RADBValid
154.89.56.0/23RADBValid
154.89.58.0/23RADBValid
154.89.60.0/22RADBValid
154.89.60.0/23RADBValid
154.89.62.0/23RADBValid
175.29.108.0/23APNICValid
175.29.110.0/23APNICValid

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.