bgpreport

Network · data from 2026-11-12

AS61805 EMEX INTERNET

Registry name: AS61805 - Emex Internet, BR · PeeringDB

21IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
14Route objects not announced registered with origin AS61805, seen from no peer

Announced routes

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

131.161.156.0/22 Valid Other IRR onlyTC 672 100% 66
170.246.32.0/22 Valid Other IRR onlyTC 672 100% 66
170.247.80.0/22 Valid Other IRR onlyNTTCOM, RADB, TC 672 100% 66
45.239.224.0/22 Valid Other IRR onlyTC 671 100% 67
200.229.156.0/22 Valid Other IRR onlyNTTCOM, RADB, TC 671 100% 66
2804:1998::/32 Valid Other IRR onlyNTTCOM, RADB, TC 636 100% 67
2804:1998::/33 Valid Other IRR onlyRADB, TC 371 58% 64
2804:1998:8000::/33 Valid Other IRR onlyRADB, TC 371 58% 64
45.239.224.0/23 Valid Other IRR onlyTC 221 33% 56
45.239.224.0/24 Valid Other IRR onlyTC 221 33% 56
45.239.226.0/23 Valid Other IRR onlyTC 221 33% 56
45.239.226.0/24 Valid Other IRR onlyTC 221 33% 56
45.239.227.0/24 Valid Other IRR onlyTC 221 33% 56
170.247.80.0/23 Valid Other IRR onlyTC 221 33% 56
170.247.81.0/24 Valid Other IRR onlyTC 221 33% 56
170.247.82.0/23 Valid Other IRR onlyTC 221 33% 56
170.247.83.0/24 Valid Other IRR onlyTC 221 33% 56
200.229.156.0/23 Valid Other IRR onlyTC 221 33% 56
200.229.156.0/24 Valid Other IRR onlyRADB, TC 221 33% 56
200.229.157.0/24 Valid Other IRR onlyRADB, TC 221 33% 56
200.229.158.0/23 Valid Other IRR onlyTC 221 33% 56
200.229.158.0/24 Valid Other IRR onlyTC 221 33% 56
200.229.159.0/24 Valid Other IRR onlyRADB, TC 221 33% 56
170.247.82.0/24 Valid Other IRR onlyTC 220 33% 56

AS-SET

PeeringDB's irr_as_set for AS61805: AS-EMEX. 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 (AS61805 isn't in the set, or no route object for AS61805 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 objectsAS61805 in itNot covered
AS-EMEX 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 39 are in fix.csv.

  • Route object: RIR24
  • AS-SET: not found1
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
Route object: RIR131.161.156.0/22Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR170.246.32.0/22Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR170.247.80.0/22Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.239.224.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR200.229.156.0/22Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:1998::/32Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:1998::/33Route object only in RADB, TC. Add it in the RIR database for the space.371 of 636
Route object: RIR2804:1998:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.371 of 636
Route object: RIR45.239.224.0/23Route object only in TC. Add it in the RIR database for the space.221 of 673
Route object: RIR45.239.224.0/24Route object only in TC. Add it in the RIR database for the space.221 of 673
Route object: RIR45.239.226.0/23Route object only in TC. Add it in the RIR database for the space.221 of 673
Route object: RIR45.239.226.0/24Route object only in TC. Add it in the RIR database for the space.221 of 673
Route object: RIR45.239.227.0/24Route object only in TC. Add it in the RIR database for the space.221 of 673
Route object: RIR170.247.80.0/23Route object only in TC. Add it in the RIR database for the space.221 of 673
Route object: RIR170.247.81.0/24Route object only in TC. Add it in the RIR database for the space.221 of 673
Route object: RIR170.247.82.0/23Route object only in TC. Add it in the RIR database for the space.221 of 673
Route object: RIR170.247.83.0/24Route object only in TC. Add it in the RIR database for the space.221 of 673
Route object: RIR200.229.156.0/23Route object only in TC. Add it in the RIR database for the space.221 of 673
Route object: RIR200.229.156.0/24Route object only in RADB, TC. Add it in the RIR database for the space.221 of 673
Route object: RIR200.229.157.0/24Route object only in RADB, TC. Add it in the RIR database for the space.221 of 673
Route object: RIR200.229.158.0/23Route object only in TC. Add it in the RIR database for the space.221 of 673
Route object: RIR200.229.158.0/24Route object only in TC. Add it in the RIR database for the space.221 of 673
Route object: RIR200.229.159.0/24Route object only in RADB, TC. Add it in the RIR database for the space.221 of 673
Route object: RIR170.247.82.0/24Route object only in TC. Add it in the RIR database for the space.220 of 673
AS-SET: not foundAS-EMEXPeeringDB names AS-EMEX; no IRR database read has it.

Route objects not announced

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

45.239.225.0/24TCValid
131.161.156.0/23TCValid
131.161.156.0/24TCValid
131.161.157.0/24TCValid
131.161.158.0/23TCValid
131.161.158.0/24TCValid
131.161.159.0/24TCValid
170.246.32.0/23TCValid
170.246.32.0/24TCValid
170.246.33.0/24TCValid
170.246.34.0/23TCValid
170.246.34.0/24TCValid
170.246.35.0/24TCValid
170.247.80.0/24TCValid

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.