bgpreport

Network · data from 2026-11-12

AS270834 AS270834 - 3D COIMBRA TELECOMUNICACOES EIRELI

Registry name: AS270834 - 3D COIMBRA TELECOMUNICACOES EIRELI, BR · not in PeeringDB

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

Announced routes

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

200.229.242.0/23 No ROA Nonecovered by 200.229.240.0/22 665 99% 67
2804:7220::/33 No ROA Nonecovered by 2804:7220::/32 635 100% 67
2804:7220:8000::/33 No ROA Nonecovered by 2804:7220::/32 635 100% 67
200.229.241.0/24 No ROA Other IRR onlyRADB 669 99% 67
200.229.243.0/24 No ROA Other IRR onlyRADB 669 99% 67
200.229.240.0/24 No ROA Other IRR onlyRADB 666 99% 67
200.229.242.0/24 No ROA Other IRR onlyRADB 664 99% 67
2804:7220::/32 No ROA Other IRR onlyRADB 635 100% 67

AS-SET

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

  • ROA: none8
  • Route object: none3
  • Route object: RIR5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none200.229.242.0/23No ROA covers it. Add a ROA for AS270834, maxLength 23.665 of 673
Route object: none200.229.242.0/23No route object for it. A route object for 200.229.240.0/22 with origin AS270834 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270834 in the RIR database for the space.665 of 673
ROA: none2804:7220::/33No ROA covers it. Add a ROA for AS270834, maxLength 33.635 of 636
Route object: none2804:7220::/33No route object for it. A route object for 2804:7220::/32 with origin AS270834 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270834 in the RIR database for the space.635 of 636
ROA: none2804:7220:8000::/33No ROA covers it. Add a ROA for AS270834, maxLength 33.635 of 636
Route object: none2804:7220:8000::/33No route object for it. A route object for 2804:7220::/32 with origin AS270834 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270834 in the RIR database for the space.635 of 636
ROA: none200.229.241.0/24No ROA covers it. Add a ROA for AS270834, maxLength 24.669 of 673
Route object: RIR200.229.241.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none200.229.243.0/24No ROA covers it. Add a ROA for AS270834, maxLength 24.669 of 673
Route object: RIR200.229.243.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none200.229.240.0/24No ROA covers it. Add a ROA for AS270834, maxLength 24.666 of 673
Route object: RIR200.229.240.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none200.229.242.0/24No ROA covers it. Add a ROA for AS270834, maxLength 24.664 of 673
Route object: RIR200.229.242.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
ROA: none2804:7220::/32No ROA covers it. Add a ROA for AS270834, maxLength 32.635 of 636
Route object: RIR2804:7220::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

200.229.240.0/22RADBNo 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.