bgpreport

Network · data from 2026-11-12

AS61877 MGX Telecom

Registry name: AS61877 - MGX Telecom, BR · PeeringDB

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

Announced routes

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

200.24.89.0/24 Valid Nonecovered by 200.24.88.0/22 664 99% 67
200.24.88.0/23 Valid Nonecovered by 200.24.88.0/22 662 98% 67
186.251.72.0/22 Valid Other IRR onlyALTDB 668 99% 67
200.24.88.0/22 Valid Other IRR onlyALTDB, RADB 666 99% 67
186.251.72.0/24 Valid Other IRR onlyALTDB 665 99% 67
186.251.73.0/24 Valid Other IRR onlyALTDB 665 99% 67
186.251.74.0/24 Valid Other IRR onlyALTDB 665 99% 67
186.251.75.0/24 Valid Other IRR onlyALTDB 665 99% 67
200.24.88.0/24 Valid Other IRR onlyALTDB 664 99% 67
200.24.90.0/24 Valid Other IRR onlyALTDB 664 99% 67
200.24.91.0/24 Valid Other IRR onlyALTDB 664 99% 67
200.24.90.0/23 Valid Other IRR onlyALTDB 662 98% 67
2804:1ab4::/32 Valid Other IRR onlyALTDB, RADB 633 100% 67
2804:1ab4::/33 Valid Other IRR onlyALTDB 354 56% 65
2804:1ab4:8000::/33 Valid Other IRR onlyALTDB 353 56% 65

AS-SET

PeeringDB's irr_as_set for AS61877: AS61877:AS-SELECT. 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 (AS61877 isn't in the set, or no route object for AS61877 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 objectsAS61877 in itNot covered
AS61877:AS-SELECT In no IRR database read today.

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

  • Route object: none2
  • Route object: RIR13
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
Route object: none200.24.89.0/24No route object for it. A route object for 200.24.88.0/22 with origin AS61877 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61877 in the RIR database for the space.664 of 673
Route object: none200.24.88.0/23No route object for it. A route object for 200.24.88.0/22 with origin AS61877 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61877 in the RIR database for the space.662 of 673
Route object: RIR186.251.72.0/22Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.24.88.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR186.251.72.0/24Route object only in ALTDB. Add it in the RIR database for the space.665 of 673
Route object: RIR186.251.73.0/24Route object only in ALTDB. Add it in the RIR database for the space.665 of 673
Route object: RIR186.251.74.0/24Route object only in ALTDB. Add it in the RIR database for the space.665 of 673
Route object: RIR186.251.75.0/24Route object only in ALTDB. Add it in the RIR database for the space.665 of 673
Route object: RIR200.24.88.0/24Route object only in ALTDB. Add it in the RIR database for the space.664 of 673
Route object: RIR200.24.90.0/24Route object only in ALTDB. Add it in the RIR database for the space.664 of 673
Route object: RIR200.24.91.0/24Route object only in ALTDB. Add it in the RIR database for the space.664 of 673
Route object: RIR200.24.90.0/23Route object only in ALTDB. Add it in the RIR database for the space.662 of 673
Route object: RIR2804:1ab4::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:1ab4::/33Route object only in ALTDB. Add it in the RIR database for the space.354 of 636
Route object: RIR2804:1ab4:8000::/33Route object only in ALTDB. Add it in the RIR database for the space.353 of 636
AS-SET: not foundAS61877:AS-SELECTPeeringDB names AS61877:AS-SELECT; no IRR database read has it.

Route objects not announced

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