bgpreport

Network · data from 2026-11-12

AS268966 i9 Master - Consultoria Tecnologicas & Telecom Eireli

Registry name: AS268966 - R.R. PEREIRA- SERV DE COM MULT - EIRELI, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268966, 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.176.200.0/23 No ROA Nonecovered by 45.176.200.0/22 672 100% 67
45.176.203.0/24 No ROA Nonecovered by 45.176.200.0/22 672 100% 67
45.176.202.0/23 No ROA Nonecovered by 45.176.200.0/22 2 0%low visibility 2
45.176.201.0/24 No ROA Other IRR onlyRADB 672 100% 67
45.176.202.0/24 No ROA Other IRR onlyRADB 671 100% 67
45.176.200.0/22 No ROA Other IRR onlyRADB, TC 208 31% 56

AS-SET

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

  • ROA: none6
  • Route object: none3
  • Route object: RIR3
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none45.176.200.0/23No ROA covers it. Add a ROA for AS268966, maxLength 23.672 of 673
Route object: none45.176.200.0/23No route object for it. A route object for 45.176.200.0/22 with origin AS268966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268966 in the RIR database for the space.672 of 673
ROA: none45.176.203.0/24No ROA covers it. Add a ROA for AS268966, maxLength 24.672 of 673
Route object: none45.176.203.0/24No route object for it. A route object for 45.176.200.0/22 with origin AS268966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268966 in the RIR database for the space.672 of 673
ROA: none45.176.202.0/23No ROA covers it. Add a ROA for AS268966, maxLength 23.2 of 673
Route object: none45.176.202.0/23No route object for it. A route object for 45.176.200.0/22 with origin AS268966 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268966 in the RIR database for the space.2 of 673
ROA: none45.176.201.0/24No ROA covers it. Add a ROA for AS268966, maxLength 24.672 of 673
Route object: RIR45.176.201.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none45.176.202.0/24No ROA covers it. Add a ROA for AS268966, maxLength 24.671 of 673
Route object: RIR45.176.202.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.176.200.0/22No ROA covers it. Add a ROA for AS268966, maxLength 22.208 of 673
Route object: RIR45.176.200.0/22Route object only in RADB, TC. Add it in the RIR database for the space.208 of 673

Route objects not announced

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

45.176.200.0/24RADBNo ROA
2804:5d58::/32RADB, TCNo ROA
2804:5d58::/48RADBNo ROA
2804:5d58:8000::/34RADBNo 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.