bgpreport

Network · data from 2026-11-12

AS61758 TOP NET SERVIÇOS

Registry name: AS61758 - TOP NET SERVICOS LTDA, BR · PeeringDB

4IPv4 routes 100.0% RPKI valid · 50.0% with a route object
26IPv6 routes 100.0% RPKI valid · 3.8% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 27 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS61758, seen from no peer

Announced routes

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

131.72.68.0/24 Valid Nonecovered by 131.72.68.0/23 670 100% 67
131.72.69.0/24 Valid Nonecovered by 131.72.68.0/23 670 100% 67
2804:1bf0::/48 Valid Nonecovered by 2804:1bf0::/32 634 100% 67
2804:1bf0:b::/48 Valid Nonecovered by 2804:1bf0::/32 634 100% 67
2804:1bf0:b0::/44 Valid Nonecovered by 2804:1bf0::/32 634 100% 67
2804:1bf0:b2::/48 Valid Nonecovered by 2804:1bf0::/32 634 100% 67
2804:1bf0:b3::/48 Valid Nonecovered by 2804:1bf0::/32 634 100% 67
2804:1bf0:b4::/46 Valid Nonecovered by 2804:1bf0::/32 634 100% 67
2804:1bf0:b8::/48 Valid Nonecovered by 2804:1bf0::/32 634 100% 67
2804:1bf0:ba::/48 Valid Nonecovered by 2804:1bf0::/32 634 100% 67
2804:1bf0:bb::/48 Valid Nonecovered by 2804:1bf0::/32 634 100% 67
2804:1bf0:bc::/46 Valid Nonecovered by 2804:1bf0::/32 634 100% 67
2804:1bf0:b00::/48 Valid Nonecovered by 2804:1bf0::/32 634 100% 67
2804:1bf0:b01::/48 Valid Nonecovered by 2804:1bf0::/32 634 100% 67
2804:1bf0:b02::/48 Valid Nonecovered by 2804:1bf0::/32 634 100% 67
2804:1bf0:b03::/48 Valid Nonecovered by 2804:1bf0::/32 634 100% 67
2804:1bf0:ff00::/40 Valid Nonecovered by 2804:1bf0::/32 634 100% 67
2804:1bf0:7::/48 Valid Nonecovered by 2804:1bf0::/32 630 99% 67
2804:1bf0:a::/48 Valid Nonecovered by 2804:1bf0::/32 630 99% 67
2804:1bf0:c::/48 Valid Nonecovered by 2804:1bf0::/32 630 99% 67
2804:1bf0:2::/48 Valid Nonecovered by 2804:1bf0::/32 332 52% 65
2804:1bf0:14::/48 Valid Nonecovered by 2804:1bf0::/32 332 52% 65
2804:1bf0:16::/48 Valid Nonecovered by 2804:1bf0::/32 332 52% 65
2804:1bf0:1d::/48 Valid Nonecovered by 2804:1bf0::/32 332 52% 65
2804:1bf0:20::/47 Valid Nonecovered by 2804:1bf0::/32 332 52% 65
2804:1bf0:face::/48 Valid Nonecovered by 2804:1bf0::/32 332 52% 65
2804:1bf0:b1::/48 Valid Nonecovered by 2804:1bf0::/32 1 0%low visibility 1
131.72.68.0/23 Valid Other IRR onlyRADB 672 100% 67
131.72.70.0/23 Valid Other IRR onlyRADB 671 100% 67
2804:1bf0::/32 Valid Other IRR onlyRADB 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS61758: AS-AS61758. 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 (AS61758 isn't in the set, or no route object for AS61758 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 objectsAS61758 in itNot covered
AS-AS61758 RADB 5712,111 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 34 are in fix.csv.

  • Route object: none27
  • Route object: RIR3
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none131.72.68.0/24No route object for it. A route object for 131.72.68.0/23 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.670 of 673
Route object: none131.72.69.0/24No route object for it. A route object for 131.72.68.0/23 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.670 of 673
Route object: none2804:1bf0::/48No route object for it. A route object for 2804:1bf0::/32 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.634 of 636
Route object: none2804:1bf0:b::/48No route object for it. A route object for 2804:1bf0::/32 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.634 of 636
Route object: none2804:1bf0:b0::/44No route object for it. A route object for 2804:1bf0::/32 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.634 of 636
Route object: none2804:1bf0:b2::/48No route object for it. A route object for 2804:1bf0::/32 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.634 of 636
Route object: none2804:1bf0:b3::/48No route object for it. A route object for 2804:1bf0::/32 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.634 of 636
Route object: none2804:1bf0:b4::/46No route object for it. A route object for 2804:1bf0::/32 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.634 of 636
Route object: none2804:1bf0:b8::/48No route object for it. A route object for 2804:1bf0::/32 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.634 of 636
Route object: none2804:1bf0:ba::/48No route object for it. A route object for 2804:1bf0::/32 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.634 of 636
Route object: none2804:1bf0:bb::/48No route object for it. A route object for 2804:1bf0::/32 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.634 of 636
Route object: none2804:1bf0:bc::/46No route object for it. A route object for 2804:1bf0::/32 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.634 of 636
Route object: none2804:1bf0:b00::/48No route object for it. A route object for 2804:1bf0::/32 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.634 of 636
Route object: none2804:1bf0:b01::/48No route object for it. A route object for 2804:1bf0::/32 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.634 of 636
Route object: none2804:1bf0:b02::/48No route object for it. A route object for 2804:1bf0::/32 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.634 of 636
Route object: none2804:1bf0:b03::/48No route object for it. A route object for 2804:1bf0::/32 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.634 of 636
Route object: none2804:1bf0:ff00::/40No route object for it. A route object for 2804:1bf0::/32 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.634 of 636
Route object: none2804:1bf0:7::/48No route object for it. A route object for 2804:1bf0::/32 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.630 of 636
Route object: none2804:1bf0:a::/48No route object for it. A route object for 2804:1bf0::/32 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.630 of 636
Route object: none2804:1bf0:c::/48No route object for it. A route object for 2804:1bf0::/32 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.630 of 636
Route object: none2804:1bf0:2::/48No route object for it. A route object for 2804:1bf0::/32 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.332 of 636
Route object: none2804:1bf0:14::/48No route object for it. A route object for 2804:1bf0::/32 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.332 of 636
Route object: none2804:1bf0:16::/48No route object for it. A route object for 2804:1bf0::/32 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.332 of 636
Route object: none2804:1bf0:1d::/48No route object for it. A route object for 2804:1bf0::/32 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.332 of 636
Route object: none2804:1bf0:20::/47No route object for it. A route object for 2804:1bf0::/32 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.332 of 636
Route object: none2804:1bf0:face::/48No route object for it. A route object for 2804:1bf0::/32 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.332 of 636
Route object: none2804:1bf0:b1::/48No route object for it. A route object for 2804:1bf0::/32 with origin AS61758 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61758 in the RIR database for the space.1 of 636
Route object: RIR131.72.68.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR131.72.70.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:1bf0::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

131.72.68.0/22RADBValid
131.72.70.0/24RADBValid
131.72.71.0/24RADBValid
186.233.28.0/22RADBNo 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.