bgpreport

Network · data from 2026-11-12

AS28368

Not in the RIR AS name list · not in PeeringDB

36IPv4 routes 0.0% RPKI valid · 0.0% with a route object
3IPv6 routes 0.0% RPKI valid · 66.7% with a route object
34RPKI invalid 34 origin · 0 maxLength
5No ROA 37 with no route object for this origin
39Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS28368, seen from no peer

Announced routes

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

186.225.49.0/24 Invalid: origin Other origin onlycovered by 186.225.32.0/19 3 0%low visibility 3
186.225.61.0/24 Invalid: origin Other origin onlycovered by 186.225.32.0/19 3 0%low visibility 3
187.60.47.0/24 Invalid: origin Other origin only 3 0%low visibility 3
177.184.131.0/24 Invalid: origin Other origin only 1 0%low visibility 2
177.184.128.0/20 Invalid: origin Other origin only 0 0%low visibility 1
177.184.128.0/21 Invalid: origin Other origin only 0 0%low visibility 1
177.184.128.0/23 Invalid: origin Other origin only 0 0%low visibility 1
177.184.128.0/24 Invalid: origin Other origin only 0 0%low visibility 1
177.184.129.0/24 Invalid: origin Other origin only 0 0%low visibility 1
177.184.130.0/23 Invalid: origin Other origin only 0 0%low visibility 1
177.184.132.0/23 Invalid: origin Other origin only 0 0%low visibility 1
177.184.133.0/24 Invalid: origin Other origin only 0 0%low visibility 1
177.184.134.0/23 Invalid: origin Other origin only 0 0%low visibility 1
177.184.136.0/21 Invalid: origin Other origin only 0 0%low visibility 1
177.184.136.0/23 Invalid: origin Other origin only 0 0%low visibility 1
177.184.138.0/23 Invalid: origin Other origin only 0 0%low visibility 1
177.184.140.0/23 Invalid: origin Other origin only 0 0%low visibility 1
177.184.142.0/23 Invalid: origin Other origin only 0 0%low visibility 1
177.200.80.0/20 Invalid: origin Other origin only 0 0%low visibility 1
177.200.80.0/21 Invalid: origin Other origin only 0 0%low visibility 1
177.200.80.0/22 Invalid: origin Other origin only 0 0%low visibility 1
177.200.80.0/23 Invalid: origin Other origin only 0 0%low visibility 1
177.200.82.0/23 Invalid: origin Other origin only 0 0%low visibility 1
177.200.84.0/22 Invalid: origin Other origin only 0 0%low visibility 1
177.200.84.0/23 Invalid: origin Other origin only 0 0%low visibility 1
177.200.85.0/24 Invalid: origin Other origin only 0 0%low visibility 1
177.200.86.0/23 Invalid: origin Other origin only 0 0%low visibility 1
177.200.88.0/21 Invalid: origin Other origin only 0 0%low visibility 1
177.200.88.0/22 Invalid: origin Other origin only 0 0%low visibility 1
177.200.88.0/23 Invalid: origin Other origin only 0 0%low visibility 1
177.200.90.0/23 Invalid: origin Other origin only 0 0%low visibility 1
177.200.92.0/22 Invalid: origin Other origin only 0 0%low visibility 1
177.200.92.0/23 Invalid: origin Other origin only 0 0%low visibility 1
177.200.94.0/23 Invalid: origin Other origin only 0 0%low visibility 1
187.84.64.0/20 No ROA None 19 3%low visibility 11
187.84.72.0/21 No ROA Other origin only 2 0%low visibility 1
2804:854:d::/48 No ROA Nonecovered by 2804:854::/32 1 0%low visibility 1
2804:854::/32 No ROA Other IRR onlyRADB, TC 2 0%low visibility 2
2804:854:a::/48 No ROA Other IRR onlyRADB 1 0%low visibility 1

AS-SET

AS28368 isn't in PeeringDB, where networks name their 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 80 are in fix.csv.

  • ROA: origin34
  • ROA: none5
  • Route object: none37
  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin186.225.49.0/24ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.3 of 673
Route object: none186.225.49.0/24Route objects for it name AS61832. A route object for 186.225.32.0/19 with origin AS28368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28368 in the RIR database for the space.3 of 673
ROA: origin186.225.61.0/24ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.3 of 673
Route object: none186.225.61.0/24Route objects for it name AS61832. A route object for 186.225.32.0/19 with origin AS28368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28368 in the RIR database for the space.3 of 673
ROA: origin187.60.47.0/24ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.3 of 673
Route object: none187.60.47.0/24Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.3 of 673
ROA: origin177.184.131.0/24ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.1 of 673
Route object: none177.184.131.0/24Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.1 of 673
ROA: origin177.184.128.0/20ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.184.128.0/20Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.184.128.0/21ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.184.128.0/21Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.184.128.0/23ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.184.128.0/23Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.184.128.0/24ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.184.128.0/24Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.184.129.0/24ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.184.129.0/24Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.184.130.0/23ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.184.130.0/23Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.184.132.0/23ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.184.132.0/23Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.184.133.0/24ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.184.133.0/24Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.184.134.0/23ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.184.134.0/23Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.184.136.0/21ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.184.136.0/21Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.184.136.0/23ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.184.136.0/23Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.184.138.0/23ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.184.138.0/23Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.184.140.0/23ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.184.140.0/23Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.184.142.0/23ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.184.142.0/23Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.200.80.0/20ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.200.80.0/20Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.200.80.0/21ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.200.80.0/21Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.200.80.0/22ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.200.80.0/22Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.200.80.0/23ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.200.80.0/23Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.200.82.0/23ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.200.82.0/23Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.200.84.0/22ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.200.84.0/22Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.200.84.0/23ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.200.84.0/23Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.200.85.0/24ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.200.85.0/24Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.200.86.0/23ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.200.86.0/23Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.200.88.0/21ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.200.88.0/21Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.200.88.0/22ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.200.88.0/22Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.200.88.0/23ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.200.88.0/23Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.200.90.0/23ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.200.90.0/23Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.200.92.0/22ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.200.92.0/22Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.200.92.0/23ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.200.92.0/23Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: origin177.200.94.0/23ROAs covering it name AS61832, not AS28368. If AS28368 should announce it, add a ROA for AS28368.0 of 673
Route object: none177.200.94.0/23Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.0 of 673
ROA: none187.84.64.0/20No ROA covers it. Add a ROA for AS28368, maxLength 20.19 of 673
Route object: none187.84.64.0/20No route object for it. Add a route object with origin AS28368 in the RIR database for the space.19 of 673
ROA: none187.84.72.0/21No ROA covers it. Add a ROA for AS28368, maxLength 21.2 of 673
Route object: none187.84.72.0/21Route objects for it name AS61832. Add a route object with origin AS28368 in the RIR database for the space.2 of 673
ROA: none2804:854:d::/48No ROA covers it. Add a ROA for AS28368, maxLength 48.1 of 636
Route object: none2804:854:d::/48No route object for it. A route object for 2804:854::/32 with origin AS28368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28368 in the RIR database for the space.1 of 636
ROA: none2804:854::/32No ROA covers it. Add a ROA for AS28368, maxLength 32.2 of 636
Route object: RIR2804:854::/32Route object only in RADB, TC. Add it in the RIR database for the space.2 of 636
ROA: none2804:854:a::/48No ROA covers it. Add a ROA for AS28368, maxLength 48.1 of 636
Route object: RIR2804:854:a::/48Route object only in RADB. Add it in the RIR database for the space.1 of 636

Route objects not announced

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

186.225.32.0/19RADBNo ROA
2804:854:b::/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.