bgpreport

Network · data from 2026-11-12

AS268913 Ara Telecom Ltda

Registry name: AS268913 - Ara Telecom Ltda, BR · PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 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
2Route objects not announced registered with origin AS268913, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS268913, 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.175.228.0/23 Valid Other IRR onlyALTDB, RADB, TC 672 100% 67
45.175.231.0/24 Valid Other IRR onlyALTDB, TC 672 100% 66
45.175.230.0/24 Valid Other IRR onlyALTDB, TC 669 99% 67
2804:5c84::/32 Valid Other IRR onlyALTDB, RADB, TC 635 100% 69
45.175.228.0/24 Valid Other IRR onlyALTDB, TC 204 30% 56
45.175.229.0/24 Valid Other IRR onlyALTDB, TC 203 30% 56

AS-SET

PeeringDB's irr_as_set for AS268913: AS268913:AS-ARATELECOM. 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 (AS268913 isn't in the set, or no route object for AS268913 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 objectsAS268913 in itNot covered
AS268913:AS-ARATELECOM In no IRR database read today.

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

  • Route object: RIR6
  • AS-SET: not found1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: RIR45.175.228.0/23Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.175.231.0/24Route object only in ALTDB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.175.230.0/24Route object only in ALTDB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:5c84::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR45.175.228.0/24Route object only in ALTDB, TC. Add it in the RIR database for the space.204 of 673
Route object: RIR45.175.229.0/24Route object only in ALTDB, TC. Add it in the RIR database for the space.203 of 673
AS-SET: not foundAS268913:AS-ARATELECOMPeeringDB names AS268913:AS-ARATELECOM; no IRR database read has it.

Route objects not announced

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

45.175.228.0/22ALTDB, RADB, TCNo ROA
45.175.230.0/23ALTDB, RADB, TCNo 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.