bgpreport

Network · data from 2026-11-12

AS263243 BRIDGE TELECOM

Registry name: AS263243 - BRIDGE TELECOM S.A., EC · PeeringDB

5IPv4 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
0Route objects not announced registered with origin AS263243, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS263243, 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.
190.107.81.0/24 Valid Other IRR onlyRADB 665 99% 67
190.107.82.0/24 Valid Other IRR onlyRADB 661 98% 67
190.107.83.0/24 Valid Other IRR onlyRADB 661 98% 67
190.107.84.0/24 Valid Other IRR onlyRADB 660 98% 67
190.107.80.0/21 Valid Other IRR onlyRADB 220 33% 59

AS-SET

AS263243'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 5 are in fix.csv.

  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
Route object: RIR190.107.81.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR190.107.82.0/24Route object only in RADB. Add it in the RIR database for the space.661 of 673
Route object: RIR190.107.83.0/24Route object only in RADB. Add it in the RIR database for the space.661 of 673
Route object: RIR190.107.84.0/24Route object only in RADB. Add it in the RIR database for the space.660 of 673
Route object: RIR190.107.80.0/21Route object only in RADB. Add it in the RIR database for the space.220 of 673

Route objects not announced

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