bgpreport

Network · data from 2026-11-12

AS29888 UNUMGROUP

Registry name: UNUMGROUP-AS - Unum Group, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS29888, 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.186.149.0/24 No ROA Other origin only 207 31% 60
192.136.182.0/24 Valid Other origin onlycovered by 192.136.182.0/23 671 100% 66
192.136.189.0/24 Valid RIR databaseARIN 673 100% 67
192.136.190.0/23 Valid RIR databaseARIN 673 100% 67
198.51.179.0/24 Valid RIR databaseARIN, RADB 673 100% 67
192.136.180.0/22 Valid RIR databaseARIN 672 100% 67
192.136.176.0/22 Valid RIR databaseARIN 671 100% 66
192.136.180.0/23 Valid RIR databaseARIN 671 100% 66
192.136.184.0/23 Valid RIR databaseARIN 671 100% 66
192.136.186.0/24 Valid RIR databaseARIN 671 100% 66
192.136.187.0/24 Valid RIR databaseARIN 671 100% 66
192.136.188.0/24 Valid RIR databaseARIN 671 100% 67
204.10.44.0/23 Valid RIR databaseARIN, RADB 671 100% 66
204.10.46.0/24 Valid RIR databaseARIN, RADB 671 100% 66
204.10.47.0/24 Valid RIR databaseARIN 671 100% 66

AS-SET

AS29888'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 29 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: not announced26
ChangePrefix or setDetailFull-table peers
ROA: none198.186.149.0/24No ROA covers it. Add a ROA for AS29888, maxLength 24.207 of 673
Route object: none198.186.149.0/24Route objects for it name AS22934. Add a route object with origin AS29888 in the RIR database for the space.207 of 673
Route object: none192.136.182.0/24Route objects for it name AS35280. A route object for 192.136.182.0/23 with origin AS29888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29888 in the RIR database for the space.671 of 673

Route objects not announced

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

192.136.176.0/20ARINValid
192.136.176.0/23ARINValid
192.136.178.0/23ARINValid
192.136.182.0/23ARINValid
192.136.186.0/23ARINValid
192.136.188.0/23ARINValid
204.10.44.0/24ARINValid
204.10.45.0/24ARINValid
204.10.46.0/23RADBValid
2620:109:3000::/44ARINValid
2620:109:3000::/48ARINValid
2620:109:3001::/48ARINValid
2620:109:3002::/48ARINValid
2620:109:3003::/48ARINValid
2620:109:3004::/48ARINValid
2620:109:3005::/48ARINValid
2620:109:3006::/48ARINValid
2620:109:3007::/48ARINValid
2620:109:3008::/48ARINValid
2620:109:3009::/48ARINValid
2620:109:300a::/48ARINValid
2620:109:300b::/48ARINValid
2620:109:300c::/48ARINValid
2620:109:300d::/48ARINValid
2620:109:300e::/48ARINValid
2620:109:300f::/48ARINValid

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.