bgpreport

Network · data from 2026-11-12

AS264241 Netsul Servico de Provedor Ltda

Registry name: AS264241 - Netsul Servico de Provedor Ltda, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264241, 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:24c4:200::/40 Valid Nonecovered by 2804:24c4::/36 636 100% 67
2804:24c4:300::/40 Valid Nonecovered by 2804:24c4::/36 636 100% 67
138.118.4.0/22 Valid Other IRR onlyALTDB, RADB, TC 669 99% 67
138.118.6.0/23 Valid Other IRR onlyALTDB, TC 669 99% 67
168.196.8.0/22 Valid Other IRR onlyALTDB, RADB, TC 669 99% 67
168.196.11.0/24 Valid Other IRR onlyALTDB, TC 669 99% 67
138.118.4.0/23 Valid Other IRR onlyALTDB, TC 667 99% 67
168.196.8.0/23 Valid Other IRR onlyALTDB, TC 667 99% 67
2804:24c4::/32 Valid Other IRR onlyALTDB, RADB, TC 635 100% 69
2804:24c4::/36 Valid Other IRR onlyALTDB, TC 635 100% 69
2804:24c4:1000::/36 Valid Other IRR onlyALTDB 635 100% 69
2804:24c4:2000::/36 Valid Other IRR onlyALTDB, TC 635 100% 69
168.196.8.0/24 Valid Other IRR onlyALTDB, TC 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS264241: AS-NETSUL-ALL RS-NETSUL-ALL AS264241:AS-NETSUL-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 (AS264241 isn't in the set, or no route object for AS264241 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 objectsAS264241 in itNot covered
AS-NETSUL-ALL ALTDB 93211 Yes 0
RS-NETSUL-ALL A route-set, not an AS-SET; route-sets aren't expanded.
AS264241:AS-NETSUL-ALL TC 93211 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 33 are in fix.csv.

  • Route object: none2
  • Route object: RIR11
  • Route object: not announced20
ChangePrefix or setDetailFull-table peers
Route object: none2804:24c4:200::/40No route object for it. A route object for 2804:24c4::/36 with origin AS264241 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264241 in the RIR database for the space.636 of 636
Route object: none2804:24c4:300::/40No route object for it. A route object for 2804:24c4::/36 with origin AS264241 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264241 in the RIR database for the space.636 of 636
Route object: RIR138.118.4.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR138.118.6.0/23Route object only in ALTDB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR168.196.8.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR168.196.11.0/24Route object only in ALTDB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR138.118.4.0/23Route object only in ALTDB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR168.196.8.0/23Route object only in ALTDB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:24c4::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:24c4::/36Route object only in ALTDB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:24c4:1000::/36Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:24c4:2000::/36Route object only in ALTDB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR168.196.8.0/24Route object only in ALTDB, TC. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

138.118.4.0/24ALTDB, TCValid
138.118.5.0/24ALTDB, TCValid
138.118.6.0/24ALTDB, TCValid
138.118.7.0/24ALTDB, TCValid
168.196.9.0/24ALTDB, TCValid
168.196.10.0/23ALTDB, TCValid
168.196.10.0/24ALTDB, TCValid
2804:24c4:3000::/36ALTDBValid
2804:24c4:4000::/36ALTDBValid
2804:24c4:5000::/36ALTDBValid
2804:24c4:6000::/36ALTDBValid
2804:24c4:7000::/36ALTDBValid
2804:24c4:8000::/36ALTDBValid
2804:24c4:9000::/36ALTDBValid
2804:24c4:a000::/36ALTDBValid
2804:24c4:b000::/36ALTDBValid
2804:24c4:c000::/36ALTDBValid
2804:24c4:d000::/36ALTDBValid
2804:24c4:e000::/36ALTDBValid
2804:24c4:f000::/36ALTDBValid

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.