bgpreport

Network · data from 2026-11-12

AS264455 STAR MAN NET PROVEDORA DE INTERNET

Registry name: AS264455 - STAR MAN NET PROVEDORA DE INTERNET LTDA - EPP, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264455, 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:1eec:2f00::/40 Invalid: maxLength Nonecovered by 2804:1eec::/34 2 0%low visibility 2
2804:1eec:af00::/40 Invalid: maxLength Nonecovered by 2804:1eec:8000::/34 2 0%low visibility 2
132.255.36.0/22 Valid Other IRR onlyRADB 665 99% 67
2804:1eec::/34 Valid Other IRR onlyRADB 630 99% 69
2804:1eec:4000::/34 Valid Other IRR onlyRADB 630 99% 69
2804:1eec:8000::/34 Valid Other IRR onlyRADB 630 99% 69
2804:1eec:c000::/34 Valid Other IRR onlyRADB 630 99% 69
2804:1eec::/32 Valid Other IRR onlyRADB 629 99% 70
2804:1eec::/33 Valid Other IRR onlyRADB 629 99% 70
2804:1eec:8000::/33 Valid Other IRR onlyRADB 629 99% 70
132.255.36.0/23 Valid Other IRR onlyRADB 202 30% 54
132.255.38.0/23 Valid Other IRR onlyRADB 202 30% 54
132.255.36.0/24 Valid Other IRR onlyRADB 5 1%low visibility 4
132.255.37.0/24 Valid Other IRR onlyRADB 5 1%low visibility 4
132.255.38.0/24 Valid Other IRR onlyRADB 5 1%low visibility 4
132.255.39.0/24 Valid Other IRR onlyRADB 5 1%low visibility 4

AS-SET

PeeringDB's irr_as_set for AS264455: AS-STARMANBR-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 (AS264455 isn't in the set, or no route object for AS264455 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 objectsAS264455 in itNot covered
AS-STARMANBR-ALL RADB 1214 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 18 are in fix.csv.

  • ROA: maxLength2
  • Route object: none2
  • Route object: RIR14
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:1eec:2f00::/40ROA 2804:1eec::/32 AS264455 has maxLength 36; the route is a /40. Raise the maxLength, or add a ROA for 2804:1eec:2f00::/40.2 of 636
Route object: none2804:1eec:2f00::/40No route object for it. A route object for 2804:1eec::/34 with origin AS264455 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264455 in the RIR database for the space.2 of 636
ROA: maxLength2804:1eec:af00::/40ROA 2804:1eec::/32 AS264455 has maxLength 36; the route is a /40. Raise the maxLength, or add a ROA for 2804:1eec:af00::/40.2 of 636
Route object: none2804:1eec:af00::/40No route object for it. A route object for 2804:1eec:8000::/34 with origin AS264455 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264455 in the RIR database for the space.2 of 636
Route object: RIR132.255.36.0/22Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR2804:1eec::/34Route object only in RADB. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:1eec:4000::/34Route object only in RADB. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:1eec:8000::/34Route object only in RADB. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:1eec:c000::/34Route object only in RADB. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:1eec::/32Route object only in RADB. Add it in the RIR database for the space.629 of 636
Route object: RIR2804:1eec::/33Route object only in RADB. Add it in the RIR database for the space.629 of 636
Route object: RIR2804:1eec:8000::/33Route object only in RADB. Add it in the RIR database for the space.629 of 636
Route object: RIR132.255.36.0/23Route object only in RADB. Add it in the RIR database for the space.202 of 673
Route object: RIR132.255.38.0/23Route object only in RADB. Add it in the RIR database for the space.202 of 673
Route object: RIR132.255.36.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR132.255.37.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR132.255.38.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR132.255.39.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673

Route objects not announced

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