bgpreport

Network · data from 2026-11-12

AS265304 SHAREWEB TELEINFORMATICA LIMITADA - ME

Registry name: AS265304 - Brdsoft Solucoes de T.i e Telecomunicacoes LTDA, BR · PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 routes 66.7% RPKI valid · 66.7% 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
2Route objects not announced registered with origin AS265304, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS265304, 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:2dcc:a000::/35 Invalid: maxLength Nonecovered by 2804:2dcc::/32 16 3%low visibility 11
168.121.4.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
168.121.4.0/24 Valid Other IRR onlyRADB 672 100% 67
168.121.6.0/24 Valid Other IRR onlyRADB 672 100% 67
168.121.7.0/24 Valid Other IRR onlyRADB 672 100% 67
2804:2dcc::/32 Valid Other IRR onlyRADB, TC 636 100% 67
2804:2dcc:e000::/35 Valid Other IRR onlyRADB 635 100% 67
168.121.5.0/24 Valid Other IRR onlyRADB 206 31% 56

AS-SET

AS265304's PeeringDB record names no AS-SET.

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 11 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: RIR7
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:2dcc:a000::/35ROA 2804:2dcc::/32 AS265304 has maxLength 32; the route is a /35. Raise the maxLength, or add a ROA for 2804:2dcc:a000::/35.16 of 636
Route object: none2804:2dcc:a000::/35No route object for it. A route object for 2804:2dcc::/32 with origin AS265304 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265304 in the RIR database for the space.16 of 636
Route object: RIR168.121.4.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR168.121.4.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR168.121.6.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR168.121.7.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:2dcc::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:2dcc:e000::/35Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR168.121.5.0/24Route object only in RADB. Add it in the RIR database for the space.206 of 673

Route objects not announced

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

168.121.4.0/23RADBValid
168.121.6.0/23RADBValid

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.