bgpreport

Network · data from 2026-11-12

AS267197 Camoa Telecom

Registry name: AS267197 - CAMOA SERVICOS TELECOM LTDA., BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267197, 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.230.192.0/24 No ROA Nonecovered by 45.230.192.0/22 666 99% 67
45.230.192.0/23 No ROA Nonecovered by 45.230.192.0/22 120 18% 44
45.230.194.0/23 No ROA Nonecovered by 45.230.192.0/22 120 18% 44
2804:49b0::/33 No ROA Nonecovered by 2804:49b0::/32 111 17% 43
2804:49b0::/34 No ROA Nonecovered by 2804:49b0::/32 111 17% 43
45.230.193.0/24 No ROA Nonecovered by 45.230.192.0/22 9 1%low visibility 7
45.230.194.0/24 No ROA Nonecovered by 45.230.192.0/22 9 1%low visibility 7
45.230.195.0/24 No ROA Nonecovered by 45.230.192.0/22 9 1%low visibility 7
2804:49b0::/35 No ROA Nonecovered by 2804:49b0::/32 9 1%low visibility 6
45.230.192.0/22 No ROA Other IRR onlyRADB, TC 671 100% 67
2804:49b0::/32 No ROA Other IRR onlyRADB, TC 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS267197: AS267197. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS267197 isn't in the set, or no route object for AS267197 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS267197 in itNot covered
AS267197 A single AS number, not a set: AS267197 (this network), 2 route objects.

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

  • ROA: none11
  • Route object: none9
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none45.230.192.0/24No ROA covers it. Add a ROA for AS267197, maxLength 24.666 of 673
Route object: none45.230.192.0/24No route object for it. A route object for 45.230.192.0/22 with origin AS267197 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267197 in the RIR database for the space.666 of 673
ROA: none45.230.192.0/23No ROA covers it. Add a ROA for AS267197, maxLength 23.120 of 673
Route object: none45.230.192.0/23No route object for it. A route object for 45.230.192.0/22 with origin AS267197 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267197 in the RIR database for the space.120 of 673
ROA: none45.230.194.0/23No ROA covers it. Add a ROA for AS267197, maxLength 23.120 of 673
Route object: none45.230.194.0/23No route object for it. A route object for 45.230.192.0/22 with origin AS267197 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267197 in the RIR database for the space.120 of 673
ROA: none2804:49b0::/33No ROA covers it. Add a ROA for AS267197, maxLength 33.111 of 636
Route object: none2804:49b0::/33No route object for it. A route object for 2804:49b0::/32 with origin AS267197 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267197 in the RIR database for the space.111 of 636
ROA: none2804:49b0::/34No ROA covers it. Add a ROA for AS267197, maxLength 34.111 of 636
Route object: none2804:49b0::/34No route object for it. A route object for 2804:49b0::/32 with origin AS267197 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267197 in the RIR database for the space.111 of 636
ROA: none45.230.193.0/24No ROA covers it. Add a ROA for AS267197, maxLength 24.9 of 673
Route object: none45.230.193.0/24No route object for it. A route object for 45.230.192.0/22 with origin AS267197 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267197 in the RIR database for the space.9 of 673
ROA: none45.230.194.0/24No ROA covers it. Add a ROA for AS267197, maxLength 24.9 of 673
Route object: none45.230.194.0/24No route object for it. A route object for 45.230.192.0/22 with origin AS267197 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267197 in the RIR database for the space.9 of 673
ROA: none45.230.195.0/24No ROA covers it. Add a ROA for AS267197, maxLength 24.9 of 673
Route object: none45.230.195.0/24No route object for it. A route object for 45.230.192.0/22 with origin AS267197 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267197 in the RIR database for the space.9 of 673
ROA: none2804:49b0::/35No ROA covers it. Add a ROA for AS267197, maxLength 35.9 of 636
Route object: none2804:49b0::/35No route object for it. A route object for 2804:49b0::/32 with origin AS267197 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267197 in the RIR database for the space.9 of 636
ROA: none45.230.192.0/22No ROA covers it. Add a ROA for AS267197, maxLength 22.671 of 673
Route object: RIR45.230.192.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none2804:49b0::/32No ROA covers it. Add a ROA for AS267197, maxLength 32.636 of 636
Route object: RIR2804:49b0::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

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