bgpreport

Network · data from 2026-11-12

AS266389 M2B - SOLUCOES EM TECNOLOGIA

Registry name: AS266389 - M2B - SOLUCOES EM TECNOLOGIA EIRELLI ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266389, 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.189.52.0/24 Valid Nonecovered by 45.189.52.0/22 672 100% 67
45.189.53.0/24 Valid Nonecovered by 45.189.52.0/22 672 100% 67
45.189.54.0/24 Valid Nonecovered by 45.189.52.0/22 672 100% 67
45.189.55.0/24 Valid Nonecovered by 45.189.52.0/22 672 100% 67
2804:3718:f000::/36 Valid Nonecovered by 2804:3718::/32 636 100% 67
2804:3718::/34 Valid Nonecovered by 2804:3718::/32 346 54% 65
2804:3718:4000::/34 Valid Nonecovered by 2804:3718::/32 346 54% 65
2804:3718:8000::/34 Valid Nonecovered by 2804:3718::/32 346 54% 65
2804:3718:c000::/34 Valid Nonecovered by 2804:3718::/32 346 54% 65
187.87.156.0/24 Valid Nonecovered by 187.87.156.0/22 118 18% 45
187.87.157.0/24 Valid Nonecovered by 187.87.156.0/22 118 18% 45
187.87.158.0/24 Valid Nonecovered by 187.87.156.0/22 118 18% 45
187.87.159.0/24 Valid Nonecovered by 187.87.156.0/22 118 18% 45
170.81.37.0/24 Valid Nonecovered by 170.81.36.0/22 117 17% 45
45.189.52.0/22 Valid Other IRR onlyRADB, TC 672 100% 66
170.81.36.0/22 Valid Other IRR onlyRADB, TC 672 100% 66
187.87.156.0/22 Valid Other IRR onlyTC 672 100% 66
2804:3718::/32 Valid Other IRR onlyRADB, TC 634 100% 67
170.81.36.0/24 Valid Other IRR onlyRADB 120 18% 45
170.81.38.0/24 Valid Other IRR onlyRADB 120 18% 45
170.81.39.0/24 Valid Other IRR onlyRADB 120 18% 45

AS-SET

PeeringDB's irr_as_set for AS266389: AS266389. 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 (AS266389 isn't in the set, or no route object for AS266389 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 objectsAS266389 in itNot covered
AS266389 A single AS number, not a set: AS266389 (this network), 7 route objects.

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

  • Route object: none14
  • Route object: RIR7
ChangePrefix or setDetailFull-table peers
Route object: none45.189.52.0/24No route object for it. A route object for 45.189.52.0/22 with origin AS266389 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266389 in the RIR database for the space.672 of 673
Route object: none45.189.53.0/24No route object for it. A route object for 45.189.52.0/22 with origin AS266389 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266389 in the RIR database for the space.672 of 673
Route object: none45.189.54.0/24No route object for it. A route object for 45.189.52.0/22 with origin AS266389 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266389 in the RIR database for the space.672 of 673
Route object: none45.189.55.0/24No route object for it. A route object for 45.189.52.0/22 with origin AS266389 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266389 in the RIR database for the space.672 of 673
Route object: none2804:3718:f000::/36No route object for it. A route object for 2804:3718::/32 with origin AS266389 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266389 in the RIR database for the space.636 of 636
Route object: none2804:3718::/34No route object for it. A route object for 2804:3718::/32 with origin AS266389 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266389 in the RIR database for the space.346 of 636
Route object: none2804:3718:4000::/34No route object for it. A route object for 2804:3718::/32 with origin AS266389 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266389 in the RIR database for the space.346 of 636
Route object: none2804:3718:8000::/34No route object for it. A route object for 2804:3718::/32 with origin AS266389 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266389 in the RIR database for the space.346 of 636
Route object: none2804:3718:c000::/34No route object for it. A route object for 2804:3718::/32 with origin AS266389 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266389 in the RIR database for the space.346 of 636
Route object: none187.87.156.0/24No route object for it. A route object for 187.87.156.0/22 with origin AS266389 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266389 in the RIR database for the space.118 of 673
Route object: none187.87.157.0/24No route object for it. A route object for 187.87.156.0/22 with origin AS266389 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266389 in the RIR database for the space.118 of 673
Route object: none187.87.158.0/24No route object for it. A route object for 187.87.156.0/22 with origin AS266389 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266389 in the RIR database for the space.118 of 673
Route object: none187.87.159.0/24No route object for it. A route object for 187.87.156.0/22 with origin AS266389 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266389 in the RIR database for the space.118 of 673
Route object: none170.81.37.0/24No route object for it. A route object for 170.81.36.0/22 with origin AS266389 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266389 in the RIR database for the space.117 of 673
Route object: RIR45.189.52.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR170.81.36.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR187.87.156.0/22Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:3718::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR170.81.36.0/24Route object only in RADB. Add it in the RIR database for the space.120 of 673
Route object: RIR170.81.38.0/24Route object only in RADB. Add it in the RIR database for the space.120 of 673
Route object: RIR170.81.39.0/24Route object only in RADB. Add it in the RIR database for the space.120 of 673

Route objects not announced

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