bgpreport

Network · data from 2026-11-12

AS262698 MKM Internet Solution Provider

Registry name: AS262698 - MKM Internet Solution Provider Ltda, BR · PeeringDB

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

Announced routes

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

187.102.32.0/24 Valid Nonecovered by 187.102.32.0/20 671 100% 67
187.102.33.0/24 Valid Nonecovered by 187.102.32.0/20 671 100% 67
187.102.36.0/24 Valid Nonecovered by 187.102.32.0/20 670 100% 67
187.102.40.0/24 Valid Nonecovered by 187.102.32.0/20 670 100% 67
187.102.43.0/24 Valid Nonecovered by 187.102.32.0/20 670 100% 67
200.215.173.0/24 Valid Nonecovered by 200.215.172.0/22 670 100% 67
200.215.175.0/24 Valid Nonecovered by 200.215.172.0/22 670 100% 67
187.102.41.0/24 Valid Other IRR onlyTC 671 100% 67
168.228.120.0/22 Valid Other IRR onlyRADB, TC 670 100% 67
187.102.32.0/20 Valid Other IRR onlyRADB, TC 670 100% 67
200.215.172.0/22 Valid Other IRR onlyRADB, TC 670 100% 67
2804:18e0::/32 Valid Other IRR onlyRADB, TC 631 99% 67
2804:18e0::/33 Valid Other IRR onlyTC 631 99% 67
2804:18e0:8000::/33 Valid Other IRR onlyTC 631 99% 67

AS-SET

PeeringDB's irr_as_set for AS262698: AS-MKM. 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 (AS262698 isn't in the set, or no route object for AS262698 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 objectsAS262698 in itNot covered
AS-MKM RIPE 213 No 14

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

  • Route object: none7
  • Route object: RIR7
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
Route object: none187.102.32.0/24No route object for it. A route object for 187.102.32.0/20 with origin AS262698 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262698 in the RIR database for the space.671 of 673
Route object: none187.102.33.0/24No route object for it. A route object for 187.102.32.0/20 with origin AS262698 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262698 in the RIR database for the space.671 of 673
Route object: none187.102.36.0/24No route object for it. A route object for 187.102.32.0/20 with origin AS262698 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262698 in the RIR database for the space.670 of 673
Route object: none187.102.40.0/24No route object for it. A route object for 187.102.32.0/20 with origin AS262698 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262698 in the RIR database for the space.670 of 673
Route object: none187.102.43.0/24No route object for it. A route object for 187.102.32.0/20 with origin AS262698 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262698 in the RIR database for the space.670 of 673
Route object: none200.215.173.0/24No route object for it. A route object for 200.215.172.0/22 with origin AS262698 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262698 in the RIR database for the space.670 of 673
Route object: none200.215.175.0/24No route object for it. A route object for 200.215.172.0/22 with origin AS262698 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262698 in the RIR database for the space.670 of 673
Route object: RIR187.102.41.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR168.228.120.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR187.102.32.0/20Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR200.215.172.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:18e0::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:18e0::/33Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:18e0:8000::/33Route object only in TC. Add it in the RIR database for the space.631 of 636
AS-SET: own ASNAS-MKMAS262698 isn't in AS-MKM (RIPE) once expanded. Add AS262698 to it.

Route objects not announced

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