bgpreport

Network · data from 2026-11-12

AS53779 BOMGAR

Registry name: BOMGAR - Bomgar Corporation, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS53779, 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.
2620:104:600b::/48 No ROA None 635 100% 67
2620:104:600c::/48 No ROA Other IRR onlyRADB 635 100% 68
2620:104:600d::/48 No ROA Other IRR onlyRADB 635 100% 68
162.253.2.0/24 No ROA RIR databaseARIN 673 100% 67
162.253.0.0/24 No ROA RIR databaseARIN 672 100% 67
2620:104:6000::/48 No ROA RIR databaseARIN 605 95% 67
2620:104:600a::/48 No ROA RIR databaseARIN 605 95% 67
162.253.1.0/24 Valid RIR databaseARIN 672 100% 67
2620:104:6001::/48 Valid RIR databaseARIN 636 100% 67

AS-SET

AS53779'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 12 are in fix.csv.

  • ROA: none7
  • Route object: none1
  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2620:104:600b::/48No ROA covers it. Add a ROA for AS53779, maxLength 48.635 of 636
Route object: none2620:104:600b::/48No route object for it. Add a route object with origin AS53779 in the RIR database for the space.635 of 636
ROA: none2620:104:600c::/48No ROA covers it. Add a ROA for AS53779, maxLength 48.635 of 636
Route object: RIR2620:104:600c::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2620:104:600d::/48No ROA covers it. Add a ROA for AS53779, maxLength 48.635 of 636
Route object: RIR2620:104:600d::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none162.253.2.0/24No ROA covers it. Add a ROA for AS53779, maxLength 24.673 of 673
ROA: none162.253.0.0/24No ROA covers it. Add a ROA for AS53779, maxLength 24.672 of 673
ROA: none2620:104:6000::/48No ROA covers it. Add a ROA for AS53779, maxLength 48.605 of 636
ROA: none2620:104:600a::/48No ROA covers it. Add a ROA for AS53779, maxLength 48.605 of 636

Route objects not announced

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

2620:104:6008::/48RADBNo ROA
2620:104:6009::/48RADBNo 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.