bgpreport

Network · data from 2026-11-12

AS5626 ONI ONITELECOM - INFOCOMUNICACOES, S.A.

Registry name: ONI ONITELECOM - INFOCOMUNICACOES, S.A., PT · not in PeeringDB

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

Announced routes

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

89.26.128.0/17 Valid RIR databaseRIPE 671 100% 67
89.26.129.0/24 Valid RIR databaseRIPE 671 100% 68
89.26.136.0/24 Valid RIR databaseRIPE 671 100% 68
89.26.137.0/24 Valid RIR databaseRIPE 671 100% 68
89.26.141.0/24 Valid RIR databaseRIPE 671 100% 68
194.38.128.0/19 Valid RIR databaseRIPE 671 100% 67
213.146.192.0/19 Valid RIR databaseRIPE 671 100% 67
89.26.128.0/24 Valid RIR databaseRIPE 668 99% 68
89.26.132.0/24 Valid RIR databaseRIPE 668 99% 68
89.26.138.0/24 Valid RIR databaseRIPE 668 99% 68
89.26.139.0/24 Valid RIR databaseRIPE 668 99% 68
89.26.140.0/24 Valid RIR databaseRIPE 668 99% 68
89.26.142.0/23 Valid RIR databaseRIPE 668 99% 68
213.146.192.0/22 Valid RIR databaseRIPE 667 99% 67

AS-SET

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

  • Route object: not announced34

Route objects not announced

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

89.26.128.0/18RIPEValid
89.26.128.0/22RIPEValid
89.26.132.0/22RIPEValid
89.26.136.0/22RIPEValid
89.26.140.0/22RIPEValid
89.26.192.0/18RIPEValid
89.26.192.0/22RIPEValid
89.26.196.0/22RIPEValid
89.26.200.0/22RIPEValid
89.26.204.0/22RIPEValid
89.26.208.0/22RIPEValid
89.26.212.0/22RIPEValid
89.26.216.0/22RIPEValid
89.26.220.0/22RIPEValid
89.26.224.0/22RIPEValid
89.26.228.0/22RIPEValid
89.26.232.0/22RIPEValid
89.26.236.0/22RIPEValid
89.26.240.0/22RIPEValid
89.26.244.0/22RIPEValid
89.26.248.0/22RIPEValid
89.26.252.0/22RIPEValid
194.38.128.0/20RIPEValid
194.38.144.0/20RIPEValid
213.146.192.0/20RIPEValid
213.146.200.0/22RIPEValid
213.146.204.0/22RIPEValid
213.146.208.0/20RIPEValid
213.146.208.0/22RIPEValid
213.146.212.0/22RIPEValid
213.146.216.0/22RIPEValid
213.146.220.0/23RIPEValid
213.146.220.0/24RIPEValid
213.146.221.0/24RIPEValid

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.