bgpreport

Network · data from 2026-11-12

AS61696 DOMUS TELECOM

Registry name: AS61696 - DOMUS TELECOM LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61696, 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:1ae0::/33 Valid Nonecovered by 2804:1ae0::/32 346 54% 64
2804:1ae0:8000::/33 Valid Nonecovered by 2804:1ae0::/32 346 54% 64
2804:1ae0::/35 Valid Nonecovered by 2804:1ae0::/32 306 48% 62
2804:1ae0:2000::/35 Valid Nonecovered by 2804:1ae0::/32 306 48% 62
2804:1ae0:4000::/35 Valid Nonecovered by 2804:1ae0::/32 306 48% 62
2804:1ae0:6000::/35 Valid Nonecovered by 2804:1ae0::/32 306 48% 62
2804:1ae0:8000::/35 Valid Nonecovered by 2804:1ae0::/32 306 48% 62
2804:1ae0:a000::/35 Valid Nonecovered by 2804:1ae0::/32 306 48% 62
2804:1ae0:c000::/35 Valid Nonecovered by 2804:1ae0::/32 306 48% 62
2804:1ae0:e000::/35 Valid Nonecovered by 2804:1ae0::/32 306 48% 62
138.36.232.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
201.140.248.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
2804:1ae0::/32 Valid Other IRR onlyRADB, TC 633 100% 67
138.36.232.0/24 Valid Other IRR onlyTC 168 25% 53
138.36.233.0/24 Valid Other IRR onlyTC 168 25% 53
138.36.234.0/24 Valid Other IRR onlyTC 168 25% 53
138.36.235.0/24 Valid Other IRR onlyTC 168 25% 53
201.140.248.0/24 Valid Other IRR onlyTC 168 25% 53
201.140.249.0/24 Valid Other IRR onlyTC 168 25% 53
201.140.250.0/24 Valid Other IRR onlyTC 168 25% 53
201.140.251.0/24 Valid Other IRR onlyTC 168 25% 53
138.36.234.0/23 Valid Other IRR onlyTC 107 16% 39
201.140.248.0/23 Valid Other IRR onlyTC 107 16% 39
138.36.232.0/23 Valid Other IRR onlyTC 106 16% 39
201.140.250.0/23 Valid Other IRR onlyTC 106 16% 39

AS-SET

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

  • Route object: none10
  • Route object: RIR15
ChangePrefix or setDetailFull-table peers
Route object: none2804:1ae0::/33No route object for it. A route object for 2804:1ae0::/32 with origin AS61696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61696 in the RIR database for the space.346 of 636
Route object: none2804:1ae0:8000::/33No route object for it. A route object for 2804:1ae0::/32 with origin AS61696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61696 in the RIR database for the space.346 of 636
Route object: none2804:1ae0::/35No route object for it. A route object for 2804:1ae0::/32 with origin AS61696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61696 in the RIR database for the space.306 of 636
Route object: none2804:1ae0:2000::/35No route object for it. A route object for 2804:1ae0::/32 with origin AS61696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61696 in the RIR database for the space.306 of 636
Route object: none2804:1ae0:4000::/35No route object for it. A route object for 2804:1ae0::/32 with origin AS61696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61696 in the RIR database for the space.306 of 636
Route object: none2804:1ae0:6000::/35No route object for it. A route object for 2804:1ae0::/32 with origin AS61696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61696 in the RIR database for the space.306 of 636
Route object: none2804:1ae0:8000::/35No route object for it. A route object for 2804:1ae0::/32 with origin AS61696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61696 in the RIR database for the space.306 of 636
Route object: none2804:1ae0:a000::/35No route object for it. A route object for 2804:1ae0::/32 with origin AS61696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61696 in the RIR database for the space.306 of 636
Route object: none2804:1ae0:c000::/35No route object for it. A route object for 2804:1ae0::/32 with origin AS61696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61696 in the RIR database for the space.306 of 636
Route object: none2804:1ae0:e000::/35No route object for it. A route object for 2804:1ae0::/32 with origin AS61696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61696 in the RIR database for the space.306 of 636
Route object: RIR138.36.232.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR201.140.248.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:1ae0::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
Route object: RIR138.36.232.0/24Route object only in TC. Add it in the RIR database for the space.168 of 673
Route object: RIR138.36.233.0/24Route object only in TC. Add it in the RIR database for the space.168 of 673
Route object: RIR138.36.234.0/24Route object only in TC. Add it in the RIR database for the space.168 of 673
Route object: RIR138.36.235.0/24Route object only in TC. Add it in the RIR database for the space.168 of 673
Route object: RIR201.140.248.0/24Route object only in TC. Add it in the RIR database for the space.168 of 673
Route object: RIR201.140.249.0/24Route object only in TC. Add it in the RIR database for the space.168 of 673
Route object: RIR201.140.250.0/24Route object only in TC. Add it in the RIR database for the space.168 of 673
Route object: RIR201.140.251.0/24Route object only in TC. Add it in the RIR database for the space.168 of 673
Route object: RIR138.36.234.0/23Route object only in TC. Add it in the RIR database for the space.107 of 673
Route object: RIR201.140.248.0/23Route object only in TC. Add it in the RIR database for the space.107 of 673
Route object: RIR138.36.232.0/23Route object only in TC. Add it in the RIR database for the space.106 of 673
Route object: RIR201.140.250.0/23Route object only in TC. Add it in the RIR database for the space.106 of 673

Route objects not announced

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