bgpreport

Network · data from 2026-11-12

AS267490 V7Provider

Registry name: AS267490 - C e B do Amaral Comunicacao - ME, BR · PeeringDB

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

Announced routes

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

2804:4248:ff00::/40 No ROA Nonecovered by 2804:4248::/32 628 99% 67
192.141.172.0/23 No ROA Other IRR onlyTC 672 100% 67
192.141.172.0/24 No ROA Other IRR onlyTC 672 100% 67
192.141.173.0/24 No ROA Other IRR onlyTC 671 100% 67
192.141.174.0/24 No ROA Other IRR onlyTC 671 100% 67
192.141.175.0/24 No ROA Other IRR onlyTC 666 99% 66
2804:4248::/32 No ROA Other IRR onlyRADB, TC 633 100% 67
2804:4248:8000::/48 No ROA Other IRR onlyTC 633 100% 67
2804:4248:9000::/48 No ROA Other IRR onlyTC 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS267490: AS267490:AS-V7PROVIDER. 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 (AS267490 isn't in the set, or no route object for AS267490 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 objectsAS267490 in itNot covered
AS267490:AS-V7PROVIDER TC 1212 Yes 0

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: none9
  • Route object: none1
  • Route object: RIR8
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2804:4248:ff00::/40No ROA covers it. Add a ROA for AS267490, maxLength 40.628 of 636
Route object: none2804:4248:ff00::/40No route object for it. A route object for 2804:4248::/32 with origin AS267490 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267490 in the RIR database for the space.628 of 636
ROA: none192.141.172.0/23No ROA covers it. Add a ROA for AS267490, maxLength 23.672 of 673
Route object: RIR192.141.172.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none192.141.172.0/24No ROA covers it. Add a ROA for AS267490, maxLength 24.672 of 673
Route object: RIR192.141.172.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none192.141.173.0/24No ROA covers it. Add a ROA for AS267490, maxLength 24.671 of 673
Route object: RIR192.141.173.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none192.141.174.0/24No ROA covers it. Add a ROA for AS267490, maxLength 24.671 of 673
Route object: RIR192.141.174.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none192.141.175.0/24No ROA covers it. Add a ROA for AS267490, maxLength 24.666 of 673
Route object: RIR192.141.175.0/24Route object only in TC. Add it in the RIR database for the space.666 of 673
ROA: none2804:4248::/32No ROA covers it. Add a ROA for AS267490, maxLength 32.633 of 636
Route object: RIR2804:4248::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
ROA: none2804:4248:8000::/48No ROA covers it. Add a ROA for AS267490, maxLength 48.633 of 636
Route object: RIR2804:4248:8000::/48Route object only in TC. Add it in the RIR database for the space.633 of 636
ROA: none2804:4248:9000::/48No ROA covers it. Add a ROA for AS267490, maxLength 48.633 of 636
Route object: RIR2804:4248:9000::/48Route object only in TC. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

45.176.180.0/22RADBNo ROA
192.141.172.0/22RADB, TCNo ROA
192.141.174.0/23TCNo ROA
2804:b0c::/32RADBNo 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.