bgpreport

Network · data from 2026-11-12

AS55219 Cisco Systems, Inc. - Talos

Registry name: SOURCEFIRE-LABS - Cisco Systems, Inc., US · PeeringDB

4IPv4 routes 75.0% RPKI valid · 50.0% with a route object
8IPv6 routes 100.0% RPKI valid · 25.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
0No ROA 8 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS55219, seen from no peer

Announced routes

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

12.167.151.0/24 Invalid: origin None 0 0%low visibility 1
172.110.204.0/23 Valid Nonecovered by 172.110.204.0/22 668 99% 67
2620:121:1::/48 Valid Nonecovered by 2620:121::/44 635 100% 68
2620:121:2::/48 Valid Nonecovered by 2620:121::/44 635 100% 68
2620:121:4::/48 Valid Nonecovered by 2620:121::/44 635 100% 68
2620:121:6::/48 Valid Nonecovered by 2620:121::/44 635 100% 68
2620:121:7::/48 Valid Nonecovered by 2620:121::/44 635 100% 68
2620:121::/48 Valid Nonecovered by 2620:121::/44 632 99% 68
172.110.204.0/22 Valid RIR databaseARIN 671 100% 66
198.148.78.0/23 Valid RIR databaseARIN 669 99% 67
2620:121::/44 Valid RIR databaseARIN 633 100% 67
2620:28:c000::/48 Valid RIR databaseARIN 632 99% 67

AS-SET

AS55219'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 9 are in fix.csv.

  • ROA: origin1
  • Route object: none8
ChangePrefix or setDetailFull-table peers
ROA: origin12.167.151.0/24ROAs covering it name AS7018, not AS55219. If AS55219 should announce it, add a ROA for AS55219.0 of 673
Route object: none12.167.151.0/24No route object for it. Add a route object with origin AS55219 in the RIR database for the space.0 of 673
Route object: none172.110.204.0/23No route object for it. A route object for 172.110.204.0/22 with origin AS55219 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55219 in the RIR database for the space.668 of 673
Route object: none2620:121:1::/48No route object for it. A route object for 2620:121::/44 with origin AS55219 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55219 in the RIR database for the space.635 of 636
Route object: none2620:121:2::/48No route object for it. A route object for 2620:121::/44 with origin AS55219 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55219 in the RIR database for the space.635 of 636
Route object: none2620:121:4::/48No route object for it. A route object for 2620:121::/44 with origin AS55219 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55219 in the RIR database for the space.635 of 636
Route object: none2620:121:6::/48No route object for it. A route object for 2620:121::/44 with origin AS55219 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55219 in the RIR database for the space.635 of 636
Route object: none2620:121:7::/48No route object for it. A route object for 2620:121::/44 with origin AS55219 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55219 in the RIR database for the space.635 of 636
Route object: none2620:121::/48No route object for it. A route object for 2620:121::/44 with origin AS55219 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55219 in the RIR database for the space.632 of 636

Route objects not announced

Every route object with origin AS55219 is announced.

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.