bgpreport

Network · data from 2026-11-12

AS265250 NETMAX SCM LTDA

Registry name: AS265250 - NET MAX, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265250, 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:2ce8::/33 Invalid: maxLength Nonecovered by 2804:2ce8::/32 2 0%low visibility 2
2804:2ce8:8000::/33 Invalid: maxLength Nonecovered by 2804:2ce8::/32 2 0%low visibility 2
168.0.118.0/23 Valid Nonecovered by 168.0.116.0/22 668 99% 66
168.0.116.0/24 Valid Other IRR onlyRADB 672 100% 67
168.0.117.0/24 Valid Other IRR onlyRADB 668 99% 67
168.0.119.0/24 Valid Other IRR onlyRADB 668 99% 67
168.0.116.0/22 Valid Other IRR onlyRADB, TC 667 99% 66
168.0.118.0/24 Valid Other IRR onlyRADB 667 99% 67
2804:2ce8::/32 Valid Other IRR onlyRADB, TC 629 99% 67

AS-SET

PeeringDB's irr_as_set for AS265250: TC::AS265250:AS-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 (AS265250 isn't in the set, or no route object for AS265250 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 objectsAS265250 in itNot covered
TC::AS265250:AS-ALL TC 126 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 11 are in fix.csv.

  • ROA: maxLength2
  • Route object: none3
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:2ce8::/33ROA 2804:2ce8::/32 AS265250 has maxLength 32; the route is a /33. Raise the maxLength, or add a ROA for 2804:2ce8::/33.2 of 636
Route object: none2804:2ce8::/33No route object for it. A route object for 2804:2ce8::/32 with origin AS265250 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265250 in the RIR database for the space.2 of 636
ROA: maxLength2804:2ce8:8000::/33ROA 2804:2ce8::/32 AS265250 has maxLength 32; the route is a /33. Raise the maxLength, or add a ROA for 2804:2ce8:8000::/33.2 of 636
Route object: none2804:2ce8:8000::/33No route object for it. A route object for 2804:2ce8::/32 with origin AS265250 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265250 in the RIR database for the space.2 of 636
Route object: none168.0.118.0/23No route object for it. A route object for 168.0.116.0/22 with origin AS265250 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265250 in the RIR database for the space.668 of 673
Route object: RIR168.0.116.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR168.0.117.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR168.0.119.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR168.0.116.0/22Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR168.0.118.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:2ce8::/32Route object only in RADB, TC. Add it in the RIR database for the space.629 of 636

Route objects not announced

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