bgpreport

Network · data from 2026-11-12

AS265189 i i telecom

Registry name: AS265189 - Inova Fibra, BR · PeeringDB

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

Announced routes

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

168.228.28.0/22 No ROA Other origin only 247 37% 59
167.250.44.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
167.250.44.0/24 Valid Other IRR onlyTC 672 100% 67
170.244.100.0/22 Valid Other IRR onlyRADB, TC 670 100% 66
170.244.100.0/24 Valid Other IRR onlyTC 670 100% 67
2804:2c08::/32 Valid Other IRR onlyTC 632 99% 67
167.250.44.0/23 Valid Other IRR onlyTC 119 18% 41
170.244.102.0/23 Valid Other IRR onlyTC 119 18% 41
167.250.46.0/23 Valid Other IRR onlyTC 118 18% 41
170.244.100.0/23 Valid Other IRR onlyTC 118 18% 41
167.250.45.0/24 Valid Other IRR onlyTC 21 3%low visibility 10
167.250.46.0/24 Valid Other IRR onlyTC 21 3%low visibility 10
167.250.47.0/24 Valid Other IRR onlyTC 21 3%low visibility 10
2804:2c08::/33 Valid Other IRR onlyTC 16 3%low visibility 8
2804:2c08:8000::/33 Valid Other IRR onlyTC 16 3%low visibility 8
170.244.101.0/24 Valid Other IRR onlyTC 12 2%low visibility 6
170.244.102.0/24 Valid Other IRR onlyTC 12 2%low visibility 6
170.244.103.0/24 Valid Other IRR onlyTC 12 2%low visibility 6

AS-SET

PeeringDB's irr_as_set for AS265189: AS-INOVAINTERNET. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS265189 isn't in the set, or no route object for AS265189 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS265189 in itNot covered
AS-INOVAINTERNET In no IRR database read today.

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

  • ROA: none1
  • Route object: none1
  • Route object: RIR17
  • AS-SET: not found1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none168.228.28.0/22No ROA covers it. Add a ROA for AS265189, maxLength 22.247 of 673
Route object: none168.228.28.0/22Route objects for it name AS264903. Add a route object with origin AS265189 in the RIR database for the space.247 of 673
Route object: RIR167.250.44.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR167.250.44.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR170.244.100.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR170.244.100.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:2c08::/32Route object only in TC. Add it in the RIR database for the space.632 of 636
Route object: RIR167.250.44.0/23Route object only in TC. Add it in the RIR database for the space.119 of 673
Route object: RIR170.244.102.0/23Route object only in TC. Add it in the RIR database for the space.119 of 673
Route object: RIR167.250.46.0/23Route object only in TC. Add it in the RIR database for the space.118 of 673
Route object: RIR170.244.100.0/23Route object only in TC. Add it in the RIR database for the space.118 of 673
Route object: RIR167.250.45.0/24Route object only in TC. Add it in the RIR database for the space.21 of 673
Route object: RIR167.250.46.0/24Route object only in TC. Add it in the RIR database for the space.21 of 673
Route object: RIR167.250.47.0/24Route object only in TC. Add it in the RIR database for the space.21 of 673
Route object: RIR2804:2c08::/33Route object only in TC. Add it in the RIR database for the space.16 of 636
Route object: RIR2804:2c08:8000::/33Route object only in TC. Add it in the RIR database for the space.16 of 636
Route object: RIR170.244.101.0/24Route object only in TC. Add it in the RIR database for the space.12 of 673
Route object: RIR170.244.102.0/24Route object only in TC. Add it in the RIR database for the space.12 of 673
Route object: RIR170.244.103.0/24Route object only in TC. Add it in the RIR database for the space.12 of 673
AS-SET: not foundAS-INOVAINTERNETPeeringDB names AS-INOVAINTERNET; no IRR database read has it.

Route objects not announced

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

2804:2c08::/34TCValid
2804:2c08:4000::/34TCValid
2804:2c08:8000::/34TCValid
2804:2c08:c000::/34TCValid

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.