bgpreport

Network · data from 2026-11-12

AS264936 FIBRA ONDA MAIS

Registry name: AS264936 - FIBRA ONDA MAIS LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264936, 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:3034:2000::/44 Invalid: maxLength Nonecovered by 2804:3034::/32 37 6%low visibility 23
168.232.80.0/22 Valid Other IRR onlyRADB, TC 668 99% 67
2804:3034::/32 Valid Other IRR onlyRADB, TC 631 99% 67
2804:3034::/44 Valid Other IRR onlyRADB, TC 631 99% 67
2804:3034:10::/44 Valid Other IRR onlyRADB, TC 631 99% 67
2804:3034:20::/44 Valid Other IRR onlyRADB, TC 631 99% 67
2804:3034:30::/44 Valid Other IRR onlyRADB, TC 631 99% 67
2804:3034:40::/44 Valid Other IRR onlyRADB, TC 631 99% 67
2804:3034:50::/44 Valid Other IRR onlyRADB, TC 631 99% 67
2804:3034:60::/44 Valid Other IRR onlyRADB, TC 631 99% 67
2804:3034:110::/44 Valid Other IRR onlyRADB, TC 631 99% 67
2804:3034:120::/43 Valid Other IRR onlyRADB, TC 631 99% 67
168.232.80.0/24 Valid Other IRR onlyTC 122 18% 41
168.232.82.0/24 Valid Other IRR onlyTC 122 18% 41
168.232.80.0/23 Valid Other IRR onlyRADB, TC 121 18% 41
168.232.81.0/24 Valid Other IRR onlyTC 121 18% 41
168.232.82.0/23 Valid Other IRR onlyRADB, TC 121 18% 41
168.232.83.0/24 Valid Other IRR onlyRADB, TC 121 18% 41

AS-SET

PeeringDB's irr_as_set for AS264936: TC::AS264936:AS-ONDAMAIS. 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 (AS264936 isn't in the set, or no route object for AS264936 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 objectsAS264936 in itNot covered
TC::AS264936:AS-ONDAMAIS TC 4238 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 19 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: RIR17
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:3034:2000::/44ROA 2804:3034::/32 AS264936 has maxLength 32; the route is a /44. Raise the maxLength, or add a ROA for 2804:3034:2000::/44.37 of 636
Route object: none2804:3034:2000::/44No route object for it. A route object for 2804:3034::/32 with origin AS264936 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264936 in the RIR database for the space.37 of 636
Route object: RIR168.232.80.0/22Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:3034::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:3034::/44Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:3034:10::/44Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:3034:20::/44Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:3034:30::/44Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:3034:40::/44Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:3034:50::/44Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:3034:60::/44Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:3034:110::/44Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:3034:120::/43Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR168.232.80.0/24Route object only in TC. Add it in the RIR database for the space.122 of 673
Route object: RIR168.232.82.0/24Route object only in TC. Add it in the RIR database for the space.122 of 673
Route object: RIR168.232.80.0/23Route object only in RADB, TC. Add it in the RIR database for the space.121 of 673
Route object: RIR168.232.81.0/24Route object only in TC. Add it in the RIR database for the space.121 of 673
Route object: RIR168.232.82.0/23Route object only in RADB, TC. Add it in the RIR database for the space.121 of 673
Route object: RIR168.232.83.0/24Route object only in RADB, TC. Add it in the RIR database for the space.121 of 673

Route objects not announced

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