bgpreport

Network · data from 2026-11-12

AS269553 REDE ONLINE INTERNET

Registry name: AS269553 - REDE ONLINE INTERNET LTDA, BR · PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
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
20Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS269553, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS269553, 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.
45.185.192.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
2804:665c::/32 Valid Other IRR onlyRADB, TC 633 100% 67
45.185.193.0/24 Valid Other IRR onlyRADB 194 29% 55
45.185.194.0/24 Valid Other IRR onlyRADB 194 29% 55
45.185.195.0/24 Valid Other IRR onlyRADB 194 29% 55
45.185.192.0/24 Valid Other IRR onlyRADB 193 29% 55
45.185.192.0/23 Valid Other IRR onlyRADB 122 18% 41
45.185.194.0/23 Valid Other IRR onlyRADB 122 18% 41
2804:665c::/33 Valid Other IRR onlyRADB 114 18% 41
2804:665c:8000::/33 Valid Other IRR onlyRADB 114 18% 41
2804:665c::/34 Valid Other IRR onlyRADB 61 10%low visibility 32
2804:665c::/36 Valid Other IRR onlyRADB 61 10%low visibility 32
2804:665c:1000::/36 Valid Other IRR onlyRADB 61 10%low visibility 32
2804:665c:2000::/36 Valid Other IRR onlyRADB 61 10%low visibility 32
2804:665c:3000::/36 Valid Other IRR onlyRADB 61 10%low visibility 32
2804:665c:4000::/34 Valid Other IRR onlyRADB 61 10%low visibility 32
2804:665c:4000::/36 Valid Other IRR onlyRADB 61 10%low visibility 32
2804:665c:5000::/36 Valid Other IRR onlyRADB 61 10%low visibility 32
2804:665c:6000::/36 Valid Other IRR onlyRADB 61 10%low visibility 32
2804:665c:7000::/36 Valid Other IRR onlyRADB 61 10%low visibility 32
2804:665c:8000::/34 Valid Other IRR onlyRADB 61 10%low visibility 32
2804:665c:8000::/36 Valid Other IRR onlyRADB 61 10%low visibility 32
2804:665c:9000::/36 Valid Other IRR onlyRADB 61 10%low visibility 32
2804:665c:a000::/36 Valid Other IRR onlyRADB 61 10%low visibility 32
2804:665c:b000::/36 Valid Other IRR onlyRADB 61 10%low visibility 32
2804:665c:c000::/34 Valid Other IRR onlyRADB 61 10%low visibility 32
2804:665c:c000::/36 Valid Other IRR onlyRADB 61 10%low visibility 32
2804:665c:d000::/36 Valid Other IRR onlyRADB 61 10%low visibility 32
2804:665c:e000::/36 Valid Other IRR onlyRADB 61 10%low visibility 32
2804:665c:f000::/36 Valid Other IRR onlyRADB 61 10%low visibility 32

AS-SET

PeeringDB's irr_as_set for AS269553: AS269553:AS-REDEONLINE-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 (AS269553 isn't in the set, or no route object for AS269553 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 objectsAS269553 in itNot covered
AS269553:AS-REDEONLINE-ALL RADBlists itself further down1 member set in no database: AS267942:AS-PRIMELINELATAM-ALL 3025415 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 31 are in fix.csv.

  • Route object: RIR30
  • AS-SET: missing member1
ChangePrefix or setDetailFull-table peers
Route object: RIR45.185.192.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:665c::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
Route object: RIR45.185.193.0/24Route object only in RADB. Add it in the RIR database for the space.194 of 673
Route object: RIR45.185.194.0/24Route object only in RADB. Add it in the RIR database for the space.194 of 673
Route object: RIR45.185.195.0/24Route object only in RADB. Add it in the RIR database for the space.194 of 673
Route object: RIR45.185.192.0/24Route object only in RADB. Add it in the RIR database for the space.193 of 673
Route object: RIR45.185.192.0/23Route object only in RADB. Add it in the RIR database for the space.122 of 673
Route object: RIR45.185.194.0/23Route object only in RADB. Add it in the RIR database for the space.122 of 673
Route object: RIR2804:665c::/33Route object only in RADB. Add it in the RIR database for the space.114 of 636
Route object: RIR2804:665c:8000::/33Route object only in RADB. Add it in the RIR database for the space.114 of 636
Route object: RIR2804:665c::/34Route object only in RADB. Add it in the RIR database for the space.61 of 636
Route object: RIR2804:665c::/36Route object only in RADB. Add it in the RIR database for the space.61 of 636
Route object: RIR2804:665c:1000::/36Route object only in RADB. Add it in the RIR database for the space.61 of 636
Route object: RIR2804:665c:2000::/36Route object only in RADB. Add it in the RIR database for the space.61 of 636
Route object: RIR2804:665c:3000::/36Route object only in RADB. Add it in the RIR database for the space.61 of 636
Route object: RIR2804:665c:4000::/34Route object only in RADB. Add it in the RIR database for the space.61 of 636
Route object: RIR2804:665c:4000::/36Route object only in RADB. Add it in the RIR database for the space.61 of 636
Route object: RIR2804:665c:5000::/36Route object only in RADB. Add it in the RIR database for the space.61 of 636
Route object: RIR2804:665c:6000::/36Route object only in RADB. Add it in the RIR database for the space.61 of 636
Route object: RIR2804:665c:7000::/36Route object only in RADB. Add it in the RIR database for the space.61 of 636
Route object: RIR2804:665c:8000::/34Route object only in RADB. Add it in the RIR database for the space.61 of 636
Route object: RIR2804:665c:8000::/36Route object only in RADB. Add it in the RIR database for the space.61 of 636
Route object: RIR2804:665c:9000::/36Route object only in RADB. Add it in the RIR database for the space.61 of 636
Route object: RIR2804:665c:a000::/36Route object only in RADB. Add it in the RIR database for the space.61 of 636
Route object: RIR2804:665c:b000::/36Route object only in RADB. Add it in the RIR database for the space.61 of 636
Route object: RIR2804:665c:c000::/34Route object only in RADB. Add it in the RIR database for the space.61 of 636
Route object: RIR2804:665c:c000::/36Route object only in RADB. Add it in the RIR database for the space.61 of 636
Route object: RIR2804:665c:d000::/36Route object only in RADB. Add it in the RIR database for the space.61 of 636
Route object: RIR2804:665c:e000::/36Route object only in RADB. Add it in the RIR database for the space.61 of 636
Route object: RIR2804:665c:f000::/36Route object only in RADB. Add it in the RIR database for the space.61 of 636
AS-SET: missing memberAS269553:AS-REDEONLINE-ALLAS269553:AS-REDEONLINE-ALL (RADB) lists AS267942:AS-PRIMELINELATAM-ALL; no IRR database read has it.

Route objects not announced

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