bgpreport

Network · data from 2026-11-12

AS36750 City of Mississauga

Registry name: CITY-OF-MISSISSAUGA - City of Mississauga, CA · PeeringDB

6IPv4 routes 0.0% RPKI valid · 16.7% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
6No ROA 5 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS36750, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS36750, 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.
142.240.68.0/24 No ROA Other origin onlycovered by 142.240.0.0/16 666 99% 67
142.240.69.0/24 No ROA Other origin onlycovered by 142.240.0.0/16 666 99% 67
142.240.71.0/24 No ROA Other origin onlycovered by 142.240.0.0/16 666 99% 67
142.240.72.0/24 No ROA Other origin onlycovered by 142.240.0.0/16 666 99% 67
142.240.252.0/24 No ROA Other origin onlycovered by 142.240.0.0/16 666 99% 67
142.240.0.0/16 No ROA RIR databaseARIN 671 100% 68

AS-SET

AS36750'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 11 are in fix.csv.

  • ROA: none6
  • Route object: none5
ChangePrefix or setDetailFull-table peers
ROA: none142.240.68.0/24No ROA covers it. Add a ROA for AS36750, maxLength 24.666 of 673
Route object: none142.240.68.0/24Route objects for it name AS15024. A route object for 142.240.0.0/16 with origin AS36750 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36750 in the RIR database for the space.666 of 673
ROA: none142.240.69.0/24No ROA covers it. Add a ROA for AS36750, maxLength 24.666 of 673
Route object: none142.240.69.0/24Route objects for it name AS15024. A route object for 142.240.0.0/16 with origin AS36750 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36750 in the RIR database for the space.666 of 673
ROA: none142.240.71.0/24No ROA covers it. Add a ROA for AS36750, maxLength 24.666 of 673
Route object: none142.240.71.0/24Route objects for it name AS15024. A route object for 142.240.0.0/16 with origin AS36750 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36750 in the RIR database for the space.666 of 673
ROA: none142.240.72.0/24No ROA covers it. Add a ROA for AS36750, maxLength 24.666 of 673
Route object: none142.240.72.0/24Route objects for it name AS15024. A route object for 142.240.0.0/16 with origin AS36750 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36750 in the RIR database for the space.666 of 673
ROA: none142.240.252.0/24No ROA covers it. Add a ROA for AS36750, maxLength 24.666 of 673
Route object: none142.240.252.0/24Route objects for it name AS15024. A route object for 142.240.0.0/16 with origin AS36750 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36750 in the RIR database for the space.666 of 673
ROA: none142.240.0.0/16No ROA covers it. Add a ROA for AS36750, maxLength 16.671 of 673

Route objects not announced

Every route object with origin AS36750 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.