bgpreport

Network · data from 2026-11-12

AS64123 Dodolink Internacional SRL

Registry name: AS64123 - DODOLINK INTERNACIONAL SRL, AR · PeeringDB

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

Announced routes

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

186.148.225.0/24 Valid Nonecovered by 186.148.224.0/22 670 100% 67
186.148.226.0/24 Valid Nonecovered by 186.148.224.0/22 670 100% 67
186.148.227.0/24 Valid Nonecovered by 186.148.224.0/22 670 100% 67
186.148.224.0/24 Valid Other IRR onlyRADB 666 99% 67
38.210.207.0/24 Valid RIR databaseARIN, RADB 669 99% 67
149.78.133.0/24 Valid RIR databaseARIN, RADB 669 99% 67
128.254.188.0/22 Valid RIR databaseARIN, RADB 667 99% 67
128.254.188.0/24 Valid RIR databaseARIN, RADB 667 99% 67
186.148.224.0/22 Valid RIR databaseLACNIC, RADB 667 99% 67
206.0.31.0/24 Valid RIR databaseARIN, RADB 667 99% 67
128.254.190.0/24 Valid RIR databaseARIN, RADB 666 99% 67
155.103.128.0/24 Valid RIR databaseARIN 665 99% 67
155.103.129.0/24 Valid RIR databaseARIN 665 99% 67
155.103.130.0/24 Valid RIR databaseARIN 665 99% 67
155.103.131.0/24 Valid RIR databaseARIN 665 99% 67
128.254.189.0/24 Valid RIR databaseARIN, RADB 664 99% 67
2803:1ee0::/32 Valid RIR databaseLACNIC, RADB 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS64123: AS64123:AS-GRUPOIN. 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 (AS64123 isn't in the set, or no route object for AS64123 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 objectsAS64123 in itNot covered
AS64123:AS-GRUPOIN LACNIC3 member sets in no database: AS64123:AS-18747, AS64123:AS-266777, AS64123:AS-NETALLIANCE 39384,037 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 13 are in fix.csv.

  • Route object: none3
  • Route object: RIR1
  • AS-SET: missing member3
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: none186.148.225.0/24No route object for it. A route object for 186.148.224.0/22 with origin AS64123 covers it (filters allowing more-specifics accept it). Add a route object with origin AS64123 in the RIR database for the space.670 of 673
Route object: none186.148.226.0/24No route object for it. A route object for 186.148.224.0/22 with origin AS64123 covers it (filters allowing more-specifics accept it). Add a route object with origin AS64123 in the RIR database for the space.670 of 673
Route object: none186.148.227.0/24No route object for it. A route object for 186.148.224.0/22 with origin AS64123 covers it (filters allowing more-specifics accept it). Add a route object with origin AS64123 in the RIR database for the space.670 of 673
Route object: RIR186.148.224.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
AS-SET: missing memberAS64123:AS-GRUPOINAS64123:AS-GRUPOIN (LACNIC) lists AS64123:AS-18747; no IRR database read has it.
AS-SET: missing memberAS64123:AS-GRUPOINAS64123:AS-GRUPOIN (LACNIC) lists AS64123:AS-266777; no IRR database read has it.
AS-SET: missing memberAS64123:AS-GRUPOINAS64123:AS-GRUPOIN (LACNIC) lists AS64123:AS-NETALLIANCE; no IRR database read has it.

Route objects not announced

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

45.191.84.0/22LACNICValid
128.254.188.0/23RADBValid
128.254.190.0/23RADBValid
128.254.191.0/24ARIN, RADBValid
155.103.128.0/22ARINValid
2803:ece0::/32LACNICValid

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.