bgpreport

Network · data from 2026-11-12

AS28254 Arganet Comunicação e Monitoramento Digital Ltda

Registry name: AS28254 - Arganet Comunicacao e Monitoramento Digital Ltda, BR · PeeringDB

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

Announced routes

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

177.71.16.0/21 Valid Other IRR onlyRADB, TC 672 100% 67
177.71.16.0/23 Valid Other IRR onlyTC 672 100% 67
177.71.18.0/23 Valid Other IRR onlyTC 672 100% 67
187.16.128.0/20 Valid Other IRR onlyRADB, TC 672 100% 67
187.16.128.0/23 Valid Other IRR onlyTC 672 100% 67
187.16.130.0/23 Valid Other IRR onlyTC 672 100% 67
187.16.132.0/23 Valid Other IRR onlyTC 672 100% 67
187.16.134.0/23 Valid Other IRR onlyTC 672 100% 67
187.16.136.0/23 Valid Other IRR onlyTC 672 100% 67
187.16.138.0/23 Valid Other IRR onlyTC 672 100% 67
187.16.142.0/23 Valid Other IRR onlyTC 672 100% 67
177.71.20.0/23 Valid Other IRR onlyTC 667 99% 67
177.71.22.0/23 Valid Other IRR onlyTC 667 99% 67
187.16.140.0/23 Valid Other IRR onlyTC 667 99% 67
2804:618::/32 Valid Other IRR onlyRADB, TC 634 100% 70
2804:618::/33 Valid Other IRR onlyTC 634 100% 69
2804:618:8000::/33 Valid Other IRR onlyTC 632 99% 67
2804:618::/34 Valid Other IRR onlyTC 354 56% 65
2804:618:4000::/34 Valid Other IRR onlyTC 354 56% 65
2804:618:8000::/34 Valid Other IRR onlyTC 354 56% 65
2804:618:c000::/34 Valid Other IRR onlyTC 354 56% 65
177.71.16.0/24 Valid Other IRR onlyTC 208 31% 56
177.71.17.0/24 Valid Other IRR onlyTC 208 31% 56
177.71.18.0/24 Valid Other IRR onlyTC 208 31% 56
177.71.19.0/24 Valid Other IRR onlyTC 208 31% 56
177.71.20.0/24 Valid Other IRR onlyTC 208 31% 56
177.71.21.0/24 Valid Other IRR onlyTC 208 31% 56
177.71.22.0/24 Valid Other IRR onlyTC 208 31% 56
177.71.23.0/24 Valid Other IRR onlyTC 208 31% 56
187.16.128.0/24 Valid Other IRR onlyTC 208 31% 56
187.16.129.0/24 Valid Other IRR onlyTC 208 31% 56
187.16.130.0/24 Valid Other IRR onlyTC 208 31% 56
187.16.131.0/24 Valid Other IRR onlyTC 208 31% 56
187.16.132.0/24 Valid Other IRR onlyTC 208 31% 56
187.16.133.0/24 Valid Other IRR onlyTC 208 31% 56
187.16.134.0/24 Valid Other IRR onlyTC 208 31% 56
187.16.135.0/24 Valid Other IRR onlyTC 208 31% 56
187.16.136.0/24 Valid Other IRR onlyTC 208 31% 56
187.16.137.0/24 Valid Other IRR onlyTC 208 31% 56
187.16.138.0/24 Valid Other IRR onlyTC 208 31% 56
187.16.139.0/24 Valid Other IRR onlyTC 208 31% 56
187.16.140.0/24 Valid Other IRR onlyTC 208 31% 56
187.16.141.0/24 Valid Other IRR onlyTC 208 31% 56
187.16.142.0/24 Valid Other IRR onlyTC 208 31% 56
187.16.143.0/24 Valid Other IRR onlyTC 208 31% 56

AS-SET

PeeringDB's irr_as_set for AS28254: AS28254:AS-ALL. 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 (AS28254 isn't in the set, or no route object for AS28254 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 objectsAS28254 in itNot covered
AS28254:AS-ALL TC 1245 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 45 are in fix.csv.

  • Route object: RIR45
ChangePrefix or setDetailFull-table peers
Route object: RIR177.71.16.0/21Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.71.16.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.71.18.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR187.16.128.0/20Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR187.16.128.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR187.16.130.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR187.16.132.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR187.16.134.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR187.16.136.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR187.16.138.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR187.16.142.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.71.20.0/23Route object only in TC. Add it in the RIR database for the space.667 of 673
Route object: RIR177.71.22.0/23Route object only in TC. Add it in the RIR database for the space.667 of 673
Route object: RIR187.16.140.0/23Route object only in TC. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:618::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:618::/33Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:618:8000::/33Route object only in TC. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:618::/34Route object only in TC. Add it in the RIR database for the space.354 of 636
Route object: RIR2804:618:4000::/34Route object only in TC. Add it in the RIR database for the space.354 of 636
Route object: RIR2804:618:8000::/34Route object only in TC. Add it in the RIR database for the space.354 of 636
Route object: RIR2804:618:c000::/34Route object only in TC. Add it in the RIR database for the space.354 of 636
Route object: RIR177.71.16.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR177.71.17.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR177.71.18.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR177.71.19.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR177.71.20.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR177.71.21.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR177.71.22.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR177.71.23.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR187.16.128.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR187.16.129.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR187.16.130.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR187.16.131.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR187.16.132.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR187.16.133.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR187.16.134.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR187.16.135.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR187.16.136.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR187.16.137.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR187.16.138.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR187.16.139.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR187.16.140.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR187.16.141.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR187.16.142.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR187.16.143.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673

Route objects not announced

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