bgpreport

Network · data from 2026-11-12

AS28154 AR TELECOM PROVEDOR DE INTERNET

Registry name: AS28154 - AR TELECOM PROVEDOR DE INTERNET LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28154, 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.54.64.0/22 Valid Nonecovered by 177.54.64.0/21 672 100% 67
177.54.68.0/22 Valid Nonecovered by 177.54.64.0/21 672 100% 67
187.49.212.0/22 Valid Nonecovered by 187.49.208.0/21 672 100% 67
177.54.72.0/22 Valid Other IRR onlyRADB 672 100% 66
177.54.76.0/22 Valid Other IRR onlyRADB 672 100% 66
177.54.76.0/24 Valid Other IRR onlyTC 672 100% 67
187.49.217.0/24 Valid Other IRR onlyTC 672 100% 67
187.49.220.0/24 Valid Other IRR onlyTC 672 100% 66
177.54.64.0/20 Valid Other IRR onlyRADB, TC 671 100% 67
177.54.69.0/24 Valid Other IRR onlyTC 671 100% 66
187.49.208.0/20 Valid Other IRR onlyRADB, TC 671 100% 67
187.49.208.0/23 Valid Other IRR onlyTC 671 100% 66
187.49.208.0/24 Valid Other IRR onlyTC 671 100% 66
187.49.210.0/24 Valid Other IRR onlyTC 671 100% 67
187.49.211.0/24 Valid Other IRR onlyTC 671 100% 67
187.49.215.0/24 Valid Other IRR onlyTC 671 100% 66
187.49.216.0/24 Valid Other IRR onlyTC 671 100% 67
187.49.218.0/24 Valid Other IRR onlyTC 671 100% 67
187.49.219.0/24 Valid Other IRR onlyTC 671 100% 67
177.54.64.0/21 Valid Other IRR onlyTC 670 100% 67
177.54.72.0/21 Valid Other IRR onlyTC 670 100% 67
187.49.208.0/21 Valid Other IRR onlyTC 670 100% 67
187.49.209.0/24 Valid Other IRR onlyTC 670 100% 66
187.49.216.0/21 Valid Other IRR onlyTC 670 100% 67
177.54.66.0/24 Valid Other IRR onlyTC 669 99% 67
177.54.67.0/24 Valid Other IRR onlyTC 668 99% 67
177.54.74.0/23 Valid Other IRR onlyTC 668 99% 67
2804:30b8::/32 Valid Other IRR onlyRADB, TC 633 100% 67
2804:30b8:ab::/48 Valid Other IRR onlyTC 632 99% 67
2804:30b8:bc::/48 Valid Other IRR onlyTC 632 99% 67
2804:30b8:cafe::/48 Valid Other IRR onlyTC 630 99% 67
177.54.65.0/24 Valid Other IRR onlyTC 206 31% 56
177.54.78.0/23 Valid Other IRR onlyTC 206 31% 56
187.49.222.0/23 Valid Other IRR onlyTC 206 31% 56
177.54.72.0/24 Valid Other IRR onlyTC 135 20% 45
177.54.77.0/24 Valid Other IRR onlyTC 135 20% 45

AS-SET

PeeringDB's irr_as_set for AS28154: AS28154. 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 (AS28154 isn't in the set, or no route object for AS28154 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 objectsAS28154 in itNot covered
AS28154 A single AS number, not a set: AS28154 (this network), 61 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 64 are in fix.csv.

  • Route object: none3
  • Route object: RIR33
  • Route object: not announced28
ChangePrefix or setDetailFull-table peers
Route object: none177.54.64.0/22No route object for it. A route object for 177.54.64.0/21 with origin AS28154 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28154 in the RIR database for the space.672 of 673
Route object: none177.54.68.0/22No route object for it. A route object for 177.54.64.0/21 with origin AS28154 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28154 in the RIR database for the space.672 of 673
Route object: none187.49.212.0/22No route object for it. A route object for 187.49.208.0/21 with origin AS28154 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28154 in the RIR database for the space.672 of 673
Route object: RIR177.54.72.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.54.76.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.54.76.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR187.49.217.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR187.49.220.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.54.64.0/20Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.54.69.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.49.208.0/20Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.49.208.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.49.208.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.49.210.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.49.211.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.49.215.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.49.216.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.49.218.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.49.219.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.54.64.0/21Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR177.54.72.0/21Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR187.49.208.0/21Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR187.49.209.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR187.49.216.0/21Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR177.54.66.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.54.67.0/24Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR177.54.74.0/23Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:30b8::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:30b8:ab::/48Route object only in TC. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:30b8:bc::/48Route object only in TC. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:30b8:cafe::/48Route object only in TC. Add it in the RIR database for the space.630 of 636
Route object: RIR177.54.65.0/24Route object only in TC. Add it in the RIR database for the space.206 of 673
Route object: RIR177.54.78.0/23Route object only in TC. Add it in the RIR database for the space.206 of 673
Route object: RIR187.49.222.0/23Route object only in TC. Add it in the RIR database for the space.206 of 673
Route object: RIR177.54.72.0/24Route object only in TC. Add it in the RIR database for the space.135 of 673
Route object: RIR177.54.77.0/24Route object only in TC. Add it in the RIR database for the space.135 of 673

Route objects not announced

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

177.54.64.0/23TCValid
177.54.64.0/24TCValid
177.54.66.0/23TCValid
177.54.68.0/23TCValid
177.54.68.0/24TCValid
177.54.70.0/23TCValid
177.54.70.0/24TCValid
177.54.71.0/24TCValid
177.54.72.0/23TCValid
177.54.73.0/24TCValid
177.54.74.0/24TCValid
177.54.75.0/24TCValid
177.54.76.0/23TCValid
177.54.78.0/24TCValid
177.54.79.0/24TCValid
187.49.210.0/23TCValid
187.49.212.0/23TCValid
187.49.212.0/24TCValid
187.49.213.0/24TCValid
187.49.214.0/23TCValid
187.49.214.0/24TCValid
187.49.216.0/23TCValid
187.49.218.0/23TCValid
187.49.220.0/23TCValid
187.49.221.0/24TCValid
187.49.222.0/24TCValid
187.49.223.0/24TCValid
2804:30b8:caee::/48TCValid

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.