bgpreport

Network · data from 2026-11-12

AS274610 NEXT BRASIL TELECOM LTDA

Registry name: AS274610 - NEXT BRASIL TELECOM LTDA, BR · PeeringDB

0IPv4 routes
23IPv6 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
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS274610, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS274610, 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:90f8::/32 Valid Other IRR onlyRADB 631 99% 67
2804:90f8::/33 Valid Other IRR onlyRADB 631 99% 67
2804:90f8::/34 Valid Other IRR onlyRADB 631 99% 67
2804:90f8:4000::/34 Valid Other IRR onlyRADB 631 99% 67
2804:90f8:8000::/33 Valid Other IRR onlyRADB 631 99% 67
2804:90f8:8000::/34 Valid Other IRR onlyRADB 631 99% 67
2804:90f8:c000::/34 Valid Other IRR onlyRADB 631 99% 67
2804:90f8:c000::/36 Valid Other IRR onlyRADB 342 54% 65
2804:90f8::/36 Valid Other IRR onlyRADB 341 54% 65
2804:90f8:1000::/36 Valid Other IRR onlyRADB 341 54% 65
2804:90f8:2000::/36 Valid Other IRR onlyRADB 341 54% 65
2804:90f8:3000::/36 Valid Other IRR onlyRADB 341 54% 65
2804:90f8:4000::/36 Valid Other IRR onlyRADB 341 54% 65
2804:90f8:5000::/36 Valid Other IRR onlyRADB 341 54% 65
2804:90f8:6000::/36 Valid Other IRR onlyRADB 341 54% 65
2804:90f8:7000::/36 Valid Other IRR onlyRADB 341 54% 65
2804:90f8:8000::/36 Valid Other IRR onlyRADB 341 54% 65
2804:90f8:9000::/36 Valid Other IRR onlyRADB 341 54% 65
2804:90f8:a000::/36 Valid Other IRR onlyRADB 341 54% 65
2804:90f8:b000::/36 Valid Other IRR onlyRADB 341 54% 65
2804:90f8:d000::/36 Valid Other IRR onlyRADB 341 54% 65
2804:90f8:e000::/36 Valid Other IRR onlyRADB 341 54% 65
2804:90f8:f000::/36 Valid Other IRR onlyRADB 341 54% 65

AS-SET

PeeringDB's irr_as_set for AS274610: AS274610:AS-NEXTBRASIL-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 (AS274610 isn't in the set, or no route object for AS274610 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 objectsAS274610 in itNot covered
AS274610:AS-NEXTBRASIL-ALL RADB 96120 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 23 are in fix.csv.

  • Route object: RIR23
ChangePrefix or setDetailFull-table peers
Route object: RIR2804:90f8::/32Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:90f8::/33Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:90f8::/34Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:90f8:4000::/34Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:90f8:8000::/33Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:90f8:8000::/34Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:90f8:c000::/34Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:90f8:c000::/36Route object only in RADB. Add it in the RIR database for the space.342 of 636
Route object: RIR2804:90f8::/36Route object only in RADB. Add it in the RIR database for the space.341 of 636
Route object: RIR2804:90f8:1000::/36Route object only in RADB. Add it in the RIR database for the space.341 of 636
Route object: RIR2804:90f8:2000::/36Route object only in RADB. Add it in the RIR database for the space.341 of 636
Route object: RIR2804:90f8:3000::/36Route object only in RADB. Add it in the RIR database for the space.341 of 636
Route object: RIR2804:90f8:4000::/36Route object only in RADB. Add it in the RIR database for the space.341 of 636
Route object: RIR2804:90f8:5000::/36Route object only in RADB. Add it in the RIR database for the space.341 of 636
Route object: RIR2804:90f8:6000::/36Route object only in RADB. Add it in the RIR database for the space.341 of 636
Route object: RIR2804:90f8:7000::/36Route object only in RADB. Add it in the RIR database for the space.341 of 636
Route object: RIR2804:90f8:8000::/36Route object only in RADB. Add it in the RIR database for the space.341 of 636
Route object: RIR2804:90f8:9000::/36Route object only in RADB. Add it in the RIR database for the space.341 of 636
Route object: RIR2804:90f8:a000::/36Route object only in RADB. Add it in the RIR database for the space.341 of 636
Route object: RIR2804:90f8:b000::/36Route object only in RADB. Add it in the RIR database for the space.341 of 636
Route object: RIR2804:90f8:d000::/36Route object only in RADB. Add it in the RIR database for the space.341 of 636
Route object: RIR2804:90f8:e000::/36Route object only in RADB. Add it in the RIR database for the space.341 of 636
Route object: RIR2804:90f8:f000::/36Route object only in RADB. Add it in the RIR database for the space.341 of 636

Route objects not announced

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