bgpreport

Network · data from 2026-11-12

AS52694 Nexsul

Registry name: AS52694 - NEXSUL TELECOM LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52694, 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.
177.73.36.0/22 Valid Other IRR onlyTC 670 100% 68
200.6.128.0/22 Valid Other IRR onlyTC 670 100% 68
2804:c58::/32 Valid Other IRR onlyTC 635 100% 69
177.73.36.0/23 Valid Other IRR onlyTC 7 1%low visibility 5
177.73.38.0/23 Valid Other IRR onlyTC 7 1%low visibility 5
200.6.128.0/23 Valid Other IRR onlyTC 7 1%low visibility 5
200.6.130.0/23 Valid Other IRR onlyTC 7 1%low visibility 5
2804:c58::/33 Valid Other IRR onlyTC 6 1%low visibility 5
2804:c58:8000::/33 Valid Other IRR onlyTC 6 1%low visibility 5

AS-SET

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

  • Route object: RIR9
ChangePrefix or setDetailFull-table peers
Route object: RIR177.73.36.0/22Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR200.6.128.0/22Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:c58::/32Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR177.73.36.0/23Route object only in TC. Add it in the RIR database for the space.7 of 673
Route object: RIR177.73.38.0/23Route object only in TC. Add it in the RIR database for the space.7 of 673
Route object: RIR200.6.128.0/23Route object only in TC. Add it in the RIR database for the space.7 of 673
Route object: RIR200.6.130.0/23Route object only in TC. Add it in the RIR database for the space.7 of 673
Route object: RIR2804:c58::/33Route object only in TC. Add it in the RIR database for the space.6 of 636
Route object: RIR2804:c58:8000::/33Route object only in TC. Add it in the RIR database for the space.6 of 636

Route objects not announced

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