bgpreport

Network · data from 2026-11-12

AS201907 TOV-BITIORA TOV Bitiora

Registry name: TOV-BITIORA TOV Bitiora, UA · not in PeeringDB

27IPv4 routes 7.4% RPKI valid · 7.4% with a route object
0IPv6 routes
25RPKI invalid 25 origin · 0 maxLength
0No ROA 25 with no route object for this origin
27Low visibility seen by under 10% of full-table peers
8Route objects not announced registered with origin AS201907, seen from no peer

Announced routes

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

80.174.104.0/22 Invalid: origin Other origin only 2 0%low visibility 2
84.75.18.0/24 Invalid: origin None 2 0%low visibility 2
84.75.19.0/24 Invalid: origin None 2 0%low visibility 2
84.75.34.0/24 Invalid: origin Other origin only 2 0%low visibility 2
84.75.37.0/24 Invalid: origin Other origin only 2 0%low visibility 2
84.75.38.0/24 Invalid: origin Other origin only 2 0%low visibility 2
84.75.41.0/24 Invalid: origin Other origin only 2 0%low visibility 2
84.75.42.0/24 Invalid: origin Other origin only 2 0%low visibility 2
84.75.48.0/24 Invalid: origin Other origin only 2 0%low visibility 2
84.75.50.0/24 Invalid: origin None 2 0%low visibility 2
84.75.51.0/24 Invalid: origin None 2 0%low visibility 2
84.75.52.0/24 Invalid: origin None 2 0%low visibility 2
84.75.53.0/24 Invalid: origin None 2 0%low visibility 2
84.75.55.0/24 Invalid: origin Other origin only 2 0%low visibility 2
84.75.61.0/24 Invalid: origin Other origin only 2 0%low visibility 2
84.75.62.0/24 Invalid: origin Other origin only 2 0%low visibility 2
84.75.64.0/24 Invalid: origin None 2 0%low visibility 2
84.75.65.0/24 Invalid: origin None 2 0%low visibility 2
84.75.67.0/24 Invalid: origin Other origin only 2 0%low visibility 2
84.75.68.0/24 Invalid: origin None 2 0%low visibility 2
84.75.69.0/24 Invalid: origin None 2 0%low visibility 2
84.75.70.0/24 Invalid: origin Other origin only 2 0%low visibility 2
185.81.30.0/23 Invalid: origin Other origin only 2 0%low visibility 2
84.75.36.0/24 Invalid: origin Other origin only 1 0%low visibility 1
143.14.81.0/24 Invalid: origin Other origin only 1 0%low visibility 1
85.8.144.0/23 Valid Other IRR onlyRADB 2 0%low visibility 2
85.8.146.0/23 Valid Other IRR onlyRADB 2 0%low visibility 2

AS-SET

AS201907 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 60 are in fix.csv.

  • ROA: origin25
  • Route object: none25
  • Route object: RIR2
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: origin80.174.104.0/22ROAs covering it name AS834, not AS201907. If AS201907 should announce it, add a ROA for AS201907.2 of 673
Route object: none80.174.104.0/22Route objects for it name AS834. Add a route object with origin AS201907 in the RIR database for the space.2 of 673
ROA: origin84.75.18.0/24ROAs covering it name AS834, not AS201907. If AS201907 should announce it, add a ROA for AS201907.2 of 673
Route object: none84.75.18.0/24No route object for it. Add a route object with origin AS201907 in the RIR database for the space.2 of 673
ROA: origin84.75.19.0/24ROAs covering it name AS834, not AS201907. If AS201907 should announce it, add a ROA for AS201907.2 of 673
Route object: none84.75.19.0/24No route object for it. Add a route object with origin AS201907 in the RIR database for the space.2 of 673
ROA: origin84.75.34.0/24ROAs covering it name AS834, not AS201907. If AS201907 should announce it, add a ROA for AS201907.2 of 673
Route object: none84.75.34.0/24Route objects for it name AS834. Add a route object with origin AS201907 in the RIR database for the space.2 of 673
ROA: origin84.75.37.0/24ROAs covering it name AS834, not AS201907. If AS201907 should announce it, add a ROA for AS201907.2 of 673
Route object: none84.75.37.0/24Route objects for it name AS834. Add a route object with origin AS201907 in the RIR database for the space.2 of 673
ROA: origin84.75.38.0/24ROAs covering it name AS834, not AS201907. If AS201907 should announce it, add a ROA for AS201907.2 of 673
Route object: none84.75.38.0/24Route objects for it name AS834. Add a route object with origin AS201907 in the RIR database for the space.2 of 673
ROA: origin84.75.41.0/24ROAs covering it name AS214647, not AS201907. If AS201907 should announce it, add a ROA for AS201907.2 of 673
Route object: none84.75.41.0/24Route objects for it name AS214647. Add a route object with origin AS201907 in the RIR database for the space.2 of 673
ROA: origin84.75.42.0/24ROAs covering it name AS834, not AS201907. If AS201907 should announce it, add a ROA for AS201907.2 of 673
Route object: none84.75.42.0/24Route objects for it name AS834. Add a route object with origin AS201907 in the RIR database for the space.2 of 673
ROA: origin84.75.48.0/24ROAs covering it name AS834, not AS201907. If AS201907 should announce it, add a ROA for AS201907.2 of 673
Route object: none84.75.48.0/24Route objects for it name AS834. Add a route object with origin AS201907 in the RIR database for the space.2 of 673
ROA: origin84.75.50.0/24ROAs covering it name AS834, not AS201907. If AS201907 should announce it, add a ROA for AS201907.2 of 673
Route object: none84.75.50.0/24No route object for it. Add a route object with origin AS201907 in the RIR database for the space.2 of 673
ROA: origin84.75.51.0/24ROAs covering it name AS834, not AS201907. If AS201907 should announce it, add a ROA for AS201907.2 of 673
Route object: none84.75.51.0/24No route object for it. Add a route object with origin AS201907 in the RIR database for the space.2 of 673
ROA: origin84.75.52.0/24ROAs covering it name AS834, not AS201907. If AS201907 should announce it, add a ROA for AS201907.2 of 673
Route object: none84.75.52.0/24No route object for it. Add a route object with origin AS201907 in the RIR database for the space.2 of 673
ROA: origin84.75.53.0/24ROAs covering it name AS834, not AS201907. If AS201907 should announce it, add a ROA for AS201907.2 of 673
Route object: none84.75.53.0/24No route object for it. Add a route object with origin AS201907 in the RIR database for the space.2 of 673
ROA: origin84.75.55.0/24ROAs covering it name AS834, not AS201907. If AS201907 should announce it, add a ROA for AS201907.2 of 673
Route object: none84.75.55.0/24Route objects for it name AS834. Add a route object with origin AS201907 in the RIR database for the space.2 of 673
ROA: origin84.75.61.0/24ROAs covering it name AS834, not AS201907. If AS201907 should announce it, add a ROA for AS201907.2 of 673
Route object: none84.75.61.0/24Route objects for it name AS834. Add a route object with origin AS201907 in the RIR database for the space.2 of 673
ROA: origin84.75.62.0/24ROAs covering it name AS834, not AS201907. If AS201907 should announce it, add a ROA for AS201907.2 of 673
Route object: none84.75.62.0/24Route objects for it name AS834. Add a route object with origin AS201907 in the RIR database for the space.2 of 673
ROA: origin84.75.64.0/24ROAs covering it name AS834, not AS201907. If AS201907 should announce it, add a ROA for AS201907.2 of 673
Route object: none84.75.64.0/24No route object for it. Add a route object with origin AS201907 in the RIR database for the space.2 of 673
ROA: origin84.75.65.0/24ROAs covering it name AS834, not AS201907. If AS201907 should announce it, add a ROA for AS201907.2 of 673
Route object: none84.75.65.0/24No route object for it. Add a route object with origin AS201907 in the RIR database for the space.2 of 673
ROA: origin84.75.67.0/24ROAs covering it name AS834, not AS201907. If AS201907 should announce it, add a ROA for AS201907.2 of 673
Route object: none84.75.67.0/24Route objects for it name AS834. Add a route object with origin AS201907 in the RIR database for the space.2 of 673
ROA: origin84.75.68.0/24ROAs covering it name AS4766, not AS201907. If AS201907 should announce it, add a ROA for AS201907.2 of 673
Route object: none84.75.68.0/24No route object for it. Add a route object with origin AS201907 in the RIR database for the space.2 of 673
ROA: origin84.75.69.0/24ROAs covering it name AS4766, not AS201907. If AS201907 should announce it, add a ROA for AS201907.2 of 673
Route object: none84.75.69.0/24No route object for it. Add a route object with origin AS201907 in the RIR database for the space.2 of 673
ROA: origin84.75.70.0/24ROAs covering it name AS834, not AS201907. If AS201907 should announce it, add a ROA for AS201907.2 of 673
Route object: none84.75.70.0/24Route objects for it name AS834. Add a route object with origin AS201907 in the RIR database for the space.2 of 673
ROA: origin185.81.30.0/23ROAs covering it name AS834, AS199550, not AS201907. If AS201907 should announce it, add a ROA for AS201907.2 of 673
Route object: none185.81.30.0/23Route objects for it name AS199550. Add a route object with origin AS201907 in the RIR database for the space.2 of 673
ROA: origin84.75.36.0/24ROAs covering it name AS136809, not AS201907. If AS201907 should announce it, add a ROA for AS201907.1 of 673
Route object: none84.75.36.0/24Route objects for it name AS136809. Add a route object with origin AS201907 in the RIR database for the space.1 of 673
ROA: origin143.14.81.0/24ROAs covering it name AS137410, not AS201907. If AS201907 should announce it, add a ROA for AS201907.1 of 673
Route object: none143.14.81.0/24Route objects for it name AS137410. Add a route object with origin AS201907 in the RIR database for the space.1 of 673
Route object: RIR85.8.144.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR85.8.146.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

108.165.8.0/22RADBNo ROA
143.109.52.0/22RADBNo ROA
166.0.96.0/23RADBNo ROA
166.0.100.0/23RADBNo ROA
168.222.64.0/20RADBNo ROA
170.62.132.0/22RADBNo ROA
170.62.144.0/22RADBNo ROA
194.124.234.0/24RADBNo 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.