bgpreport

Network · data from 2026-11-12

AS61917 LUCARONI TELECOM

Registry name: AS61917 - NETMAIS TELECOM, BR · PeeringDB

21IPv4 routes 100.0% RPKI valid · 100.0% with a route object
6IPv6 routes 100.0% RPKI valid · 50.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
0Route objects not announced registered with origin AS61917, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS61917, 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:16cc::/36 Valid Nonecovered by 2804:16cc::/33 109 17% 43
2804:16cc:1000::/36 Valid Nonecovered by 2804:16cc::/33 109 17% 43
2804:16cc:2000::/36 Valid Nonecovered by 2804:16cc::/33 109 17% 43
179.124.132.0/24 Valid Other IRR onlyRADB, TC 668 99% 67
45.188.152.0/22 Valid Other IRR onlyRADB, TC 667 99% 67
45.188.152.0/23 Valid Other IRR onlyRADB, TC 667 99% 67
167.250.56.0/22 Valid Other IRR onlyRADB, TC 667 99% 67
167.250.56.0/23 Valid Other IRR onlyRADB, TC 667 99% 67
167.250.58.0/23 Valid Other IRR onlyRADB, TC 667 99% 67
179.124.132.0/22 Valid Other IRR onlyRADB, TC 667 99% 67
179.124.132.0/23 Valid Other IRR onlyRADB, TC 667 99% 67
179.124.134.0/23 Valid Other IRR onlyRADB, TC 667 99% 67
45.188.154.0/23 Valid Other IRR onlyRADB, TC 666 99% 67
2804:16cc::/32 Valid Other IRR onlyRADB, TC 632 99% 67
45.188.152.0/24 Valid Other IRR onlyRADB, TC 119 18% 44
45.188.153.0/24 Valid Other IRR onlyRADB, TC 119 18% 44
45.188.154.0/24 Valid Other IRR onlyRADB, TC 119 18% 44
45.188.155.0/24 Valid Other IRR onlyRADB, TC 119 18% 44
167.250.56.0/24 Valid Other IRR onlyRADB, TC 119 18% 44
167.250.57.0/24 Valid Other IRR onlyRADB, TC 119 18% 44
167.250.59.0/24 Valid Other IRR onlyRADB, TC 119 18% 44
179.124.133.0/24 Valid Other IRR onlyRADB, TC 119 18% 44
179.124.134.0/24 Valid Other IRR onlyRADB, TC 119 18% 44
179.124.135.0/24 Valid Other IRR onlyRADB, TC 119 18% 44
167.250.58.0/24 Valid Other IRR onlyRADB, TC 117 17% 44
2804:16cc::/33 Valid Other IRR onlyRADB, TC 109 17% 43
2804:16cc:8000::/33 Valid Other IRR onlyRADB, TC 109 17% 43

AS-SET

PeeringDB's irr_as_set for AS61917: AS61917:AS-ANNOUNCEMENTS. 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 (AS61917 isn't in the set, or no route object for AS61917 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 objectsAS61917 in itNot covered
AS61917:AS-ANNOUNCEMENTS TC 426823 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 27 are in fix.csv.

  • Route object: none3
  • Route object: RIR24
ChangePrefix or setDetailFull-table peers
Route object: none2804:16cc::/36No route object for it. A route object for 2804:16cc::/33 with origin AS61917 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61917 in the RIR database for the space.109 of 636
Route object: none2804:16cc:1000::/36No route object for it. A route object for 2804:16cc::/33 with origin AS61917 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61917 in the RIR database for the space.109 of 636
Route object: none2804:16cc:2000::/36No route object for it. A route object for 2804:16cc::/33 with origin AS61917 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61917 in the RIR database for the space.109 of 636
Route object: RIR179.124.132.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR45.188.152.0/22Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR45.188.152.0/23Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR167.250.56.0/22Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR167.250.56.0/23Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR167.250.58.0/23Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR179.124.132.0/22Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR179.124.132.0/23Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR179.124.134.0/23Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR45.188.154.0/23Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
Route object: RIR2804:16cc::/32Route object only in RADB, TC. Add it in the RIR database for the space.632 of 636
Route object: RIR45.188.152.0/24Route object only in RADB, TC. Add it in the RIR database for the space.119 of 673
Route object: RIR45.188.153.0/24Route object only in RADB, TC. Add it in the RIR database for the space.119 of 673
Route object: RIR45.188.154.0/24Route object only in RADB, TC. Add it in the RIR database for the space.119 of 673
Route object: RIR45.188.155.0/24Route object only in RADB, TC. Add it in the RIR database for the space.119 of 673
Route object: RIR167.250.56.0/24Route object only in RADB, TC. Add it in the RIR database for the space.119 of 673
Route object: RIR167.250.57.0/24Route object only in RADB, TC. Add it in the RIR database for the space.119 of 673
Route object: RIR167.250.59.0/24Route object only in RADB, TC. Add it in the RIR database for the space.119 of 673
Route object: RIR179.124.133.0/24Route object only in RADB, TC. Add it in the RIR database for the space.119 of 673
Route object: RIR179.124.134.0/24Route object only in RADB, TC. Add it in the RIR database for the space.119 of 673
Route object: RIR179.124.135.0/24Route object only in RADB, TC. Add it in the RIR database for the space.119 of 673
Route object: RIR167.250.58.0/24Route object only in RADB, TC. Add it in the RIR database for the space.117 of 673
Route object: RIR2804:16cc::/33Route object only in RADB, TC. Add it in the RIR database for the space.109 of 636
Route object: RIR2804:16cc:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.109 of 636

Route objects not announced

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