bgpreport

Network · data from 2026-11-12

AS53154 MCO2 Tecnologia

Registry name: AS53154 - MCO2 Tecnologia, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS53154, 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.

186.209.224.0/20 Valid Other IRR onlyALTDB 669 99% 67
186.209.228.0/22 Valid Other IRR onlyALTDB 211 31% 56
186.209.232.0/22 Valid Other IRR onlyALTDB 211 31% 56
186.209.236.0/22 Valid Other IRR onlyALTDB 211 31% 56
186.209.224.0/22 Valid Other IRR onlyALTDB 210 31% 56

AS-SET

PeeringDB's irr_as_set for AS53154: AS-MCO2. 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 (AS53154 isn't in the set, or no route object for AS53154 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 objectsAS53154 in itNot covered
AS-MCO2 ALTDB 117 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 7 are in fix.csv.

  • Route object: RIR5
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: RIR186.209.224.0/20Route object only in ALTDB. Add it in the RIR database for the space.669 of 673
Route object: RIR186.209.228.0/22Route object only in ALTDB. Add it in the RIR database for the space.211 of 673
Route object: RIR186.209.232.0/22Route object only in ALTDB. Add it in the RIR database for the space.211 of 673
Route object: RIR186.209.236.0/22Route object only in ALTDB. Add it in the RIR database for the space.211 of 673
Route object: RIR186.209.224.0/22Route object only in ALTDB. Add it in the RIR database for the space.210 of 673

Route objects not announced

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

186.209.224.0/21ALTDBValid
186.209.232.0/21ALTDBValid

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.