bgpreport

Network · data from 2026-11-12

AS266580 AS266580 - PC INFO TELECOM EIRELI - ME

Registry name: AS266580 - PC INFO TELECOM EIRELI - ME, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266580, 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.
45.7.48.0/24 No ROA Other IRR onlyALTDB 670 100% 67
45.7.49.0/24 No ROA Other IRR onlyALTDB 670 100% 67
45.7.51.0/24 No ROA Other IRR onlyALTDB 670 100% 67
2804:3e34::/32 No ROA Other IRR onlyALTDB, RADB 636 100% 67
2804:3e34::/33 No ROA Other IRR onlyALTDB 636 100% 67
2804:3e34::/34 No ROA Other IRR onlyALTDB 636 100% 67

AS-SET

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

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none45.7.48.0/24No ROA covers it. Add a ROA for AS266580, maxLength 24.670 of 673
Route object: RIR45.7.48.0/24Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
ROA: none45.7.49.0/24No ROA covers it. Add a ROA for AS266580, maxLength 24.670 of 673
Route object: RIR45.7.49.0/24Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
ROA: none45.7.51.0/24No ROA covers it. Add a ROA for AS266580, maxLength 24.670 of 673
Route object: RIR45.7.51.0/24Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
ROA: none2804:3e34::/32No ROA covers it. Add a ROA for AS266580, maxLength 32.636 of 636
Route object: RIR2804:3e34::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.636 of 636
ROA: none2804:3e34::/33No ROA covers it. Add a ROA for AS266580, maxLength 33.636 of 636
Route object: RIR2804:3e34::/33Route object only in ALTDB. Add it in the RIR database for the space.636 of 636
ROA: none2804:3e34::/34No ROA covers it. Add a ROA for AS266580, maxLength 34.636 of 636
Route object: RIR2804:3e34::/34Route object only in ALTDB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

45.7.48.0/22ALTDB, RADBNo ROA
45.7.48.0/23ALTDBNo ROA
45.7.50.0/23ALTDBNo ROA
45.7.50.0/24ALTDBNo 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.