bgpreport

Network · data from 2026-11-12

AS268726 TOPNET SERVIÇOS DE TELECOMU E MULTIMÍDIA

Registry name: AS268726 - TOPNET SERVICOS DE TELECOMU E MULTIMIDIA EIRELI-ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268726, 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:59cc::/33 Invalid: maxLength Nonecovered by 2804:59cc::/32 46 7%low visibility 26
2804:59cc:8000::/33 Invalid: maxLength Nonecovered by 2804:59cc::/32 46 7%low visibility 26
45.171.186.0/23 Valid Other IRR onlyTC 672 100% 66
45.171.184.0/22 Valid Other IRR onlyRADB, TC 671 100% 66
45.171.184.0/23 Valid Other IRR onlyTC 671 100% 66
45.171.187.0/24 Valid Other IRR onlyTC 670 100% 66
45.171.186.0/24 Valid Other IRR onlyTC 667 99% 67
2804:59cc::/32 Valid Other IRR onlyRADB, TC 635 100% 67
2804:59cc::/34 Valid Other IRR onlyTC 347 55% 64
2804:59cc:4000::/34 Valid Other IRR onlyTC 347 55% 64
2804:59cc:8000::/34 Valid Other IRR onlyTC 347 55% 64
2804:59cc:c000::/34 Valid Other IRR onlyTC 347 55% 64
45.171.184.0/24 Valid Other IRR onlyTC 175 26% 48
45.171.185.0/24 Valid Other IRR onlyTC 175 26% 48

AS-SET

PeeringDB's irr_as_set for AS268726: AS-SET. 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 (AS268726 isn't in the set, or no route object for AS268726 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 objectsAS268726 in itNot covered
AS-SET RADB 010 No 14
AFRINIC (also) 111 No 14
ARIN (also) 010 No 14
RIPE (also)1 member set in no database: AS200105:AS-HK 38151,451 No 14

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

  • ROA: maxLength2
  • Route object: none2
  • Route object: RIR12
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:59cc::/33ROA 2804:59cc::/32 AS268726 has maxLength 32; the route is a /33. Raise the maxLength, or add a ROA for 2804:59cc::/33.46 of 636
Route object: none2804:59cc::/33No route object for it. A route object for 2804:59cc::/32 with origin AS268726 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268726 in the RIR database for the space.46 of 636
ROA: maxLength2804:59cc:8000::/33ROA 2804:59cc::/32 AS268726 has maxLength 32; the route is a /33. Raise the maxLength, or add a ROA for 2804:59cc:8000::/33.46 of 636
Route object: none2804:59cc:8000::/33No route object for it. A route object for 2804:59cc::/32 with origin AS268726 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268726 in the RIR database for the space.46 of 636
Route object: RIR45.171.186.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.171.184.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.171.184.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.171.187.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.171.186.0/24Route object only in TC. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:59cc::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:59cc::/34Route object only in TC. Add it in the RIR database for the space.347 of 636
Route object: RIR2804:59cc:4000::/34Route object only in TC. Add it in the RIR database for the space.347 of 636
Route object: RIR2804:59cc:8000::/34Route object only in TC. Add it in the RIR database for the space.347 of 636
Route object: RIR2804:59cc:c000::/34Route object only in TC. Add it in the RIR database for the space.347 of 636
Route object: RIR45.171.184.0/24Route object only in TC. Add it in the RIR database for the space.175 of 673
Route object: RIR45.171.185.0/24Route object only in TC. Add it in the RIR database for the space.175 of 673
AS-SET: own ASNAS-SETAS268726 isn't in AS-SET (RADB) once expanded. Add AS268726 to it.

Route objects not announced

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