bgpreport

Network · data from 2026-11-12

AS28398 INTERNET TELEFONIA Y TV DE MICHOACAN SA DE CV

Registry name: AS28398 - INTERNET TELEFONIA Y TV DE MICHOACAN SA DE CV, MX · PeeringDB

65IPv4 routes 63.1% RPKI valid · 63.1% with a route object
4IPv6 routes 50.0% RPKI valid · 50.0% with a route object
17RPKI invalid 16 origin · 1 maxLength
9No ROA 26 with no route object for this origin
26Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS28398, seen from no peer

Announced routes

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

1.178.72.252/31 Invalid: origin None 1 0%low visibility 1
1.178.72.254/31 Invalid: origin None 1 0%low visibility 1
45.68.64.0/24 Invalid: origin Other origin only 1 0%low visibility 1
62.115.33.170/31 Invalid: origin None 1 0%low visibility 1
63.220.204.220/30 Invalid: origin None 1 0%low visibility 1
64.86.54.44/31 Invalid: origin None 1 0%low visibility 1
71.18.242.16/31 Invalid: origin None 1 0%low visibility 1
72.14.243.168/31 Invalid: origin None 1 0%low visibility 1
79.140.89.156/31 Invalid: origin None 1 0%low visibility 1
94.142.103.190/31 Invalid: origin None 1 0%low visibility 1
128.241.8.20/31 Invalid: origin None 1 0%low visibility 1
138.122.99.152/31 Invalid: origin None 1 0%low visibility 1
184.105.12.224/30 Invalid: origin None 1 0%low visibility 1
200.25.32.96/31 Invalid: origin None 1 0%low visibility 1
206.72.210.0/23 Invalid: origin None 1 0%low visibility 1
208.184.124.112/31 Invalid: origin None 1 0%low visibility 1
2806:206:0:4000::120/124 Invalid: maxLength Nonecovered by 2806:206::/32 1 0%low visibility 1
0.0.0.0/0 bogon No ROA None 1 0%low visibility 1
10.141.141.0/24 bogon No ROA None 1 0%low visibility 1
192.168.19.252/30 bogon No ROA None 1 0%low visibility 1
192.168.20.252/30 bogon No ROA None 1 0%low visibility 1
::/0 bogon No ROA None 1 0%low visibility 1
8.243.210.240/30 No ROA None 1 0%low visibility 1
38.32.254.134/31 No ROA None 1 0%low visibility 1
65.175.54.164/30 No ROA None 1 0%low visibility 1
157.240.92.150/31 No ROA None 1 0%low visibility 1
38.7.16.0/24 Valid Other IRR onlyRADB 669 99% 68
38.7.17.0/24 Valid Other IRR onlyRADB 669 99% 68
38.7.18.0/24 Valid Other IRR onlyRADB 669 99% 68
38.7.19.0/24 Valid Other IRR onlyRADB 669 99% 68
38.7.20.0/24 Valid Other IRR onlyRADB 669 99% 68
38.7.21.0/24 Valid Other IRR onlyRADB 669 99% 68
38.7.22.0/24 Valid Other IRR onlyRADB 669 99% 68
38.7.23.0/24 Valid Other IRR onlyRADB 669 99% 68
38.141.80.0/20 Valid Other IRR onlyRADB 669 99% 68
38.141.80.0/24 Valid Other IRR onlyRADB 669 99% 68
38.141.81.0/24 Valid Other IRR onlyRADB 669 99% 68
38.141.82.0/24 Valid Other IRR onlyRADB 669 99% 68
38.141.83.0/24 Valid Other IRR onlyRADB 669 99% 68
38.141.84.0/24 Valid Other IRR onlyRADB 669 99% 68
38.141.85.0/24 Valid Other IRR onlyRADB 669 99% 68
38.141.86.0/24 Valid Other IRR onlyRADB 669 99% 68
38.141.87.0/24 Valid Other IRR onlyRADB 669 99% 68
38.141.88.0/24 Valid Other IRR onlyRADB 669 99% 68
38.141.89.0/24 Valid Other IRR onlyRADB 669 99% 68
38.141.90.0/24 Valid Other IRR onlyRADB 669 99% 68
38.141.91.0/24 Valid Other IRR onlyRADB 669 99% 68
38.141.92.0/24 Valid Other IRR onlyRADB 669 99% 68
38.141.93.0/24 Valid Other IRR onlyRADB 669 99% 68
38.141.94.0/24 Valid Other IRR onlyRADB 669 99% 68
38.141.95.0/24 Valid Other IRR onlyRADB 669 99% 68
164.163.188.0/24 Valid Other IRR onlyRADB 669 99% 68
164.163.189.0/24 Valid Other IRR onlyRADB 669 99% 68
164.163.190.0/24 Valid Other IRR onlyRADB 669 99% 68
164.163.191.0/24 Valid Other IRR onlyRADB 669 99% 68
206.85.9.0/24 Valid Other IRR onlyRADB 669 99% 68
206.85.10.0/24 Valid Other IRR onlyRADB 669 99% 68
206.85.11.0/24 Valid Other IRR onlyRADB 669 99% 68
206.85.8.0/24 Valid Other IRR onlyRADB 666 99% 68
38.7.16.0/21 Valid RIR databaseARIN, RADB 669 99% 68
138.99.148.0/22 Valid RIR databaseLACNIC, RADB 669 99% 68
138.99.148.0/24 Valid RIR databaseLACNIC, RADB 669 99% 68
138.99.149.0/24 Valid RIR databaseLACNIC, RADB 669 99% 68
138.99.150.0/24 Valid RIR databaseLACNIC, RADB 669 99% 68
138.99.151.0/24 Valid RIR databaseLACNIC, RADB 669 99% 68
164.163.188.0/22 Valid RIR databaseLACNIC, RADB 669 99% 68
206.85.8.0/22 Valid RIR databaseARIN, RADB 669 99% 68
2806:206::/32 Valid RIR databaseLACNIC, RADB 636 100% 69
2806:2ed::/32 Valid RIR databaseLACNIC, RADB 636 100% 69

AS-SET

PeeringDB's irr_as_set for AS28398: AS-GBIC. 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 (AS28398 isn't in the set, or no route object for AS28398 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 objectsAS28398 in itNot covered
AS-GBIC RADB 111102 Yes 26

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

  • ROA: origin16
  • ROA: maxLength1
  • Bogon prefix5
  • ROA: none4
  • Route object: none21
  • Route object: RIR33
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin1.178.72.252/31ROAs covering it name AS16509, not AS28398. If AS28398 should announce it, add a ROA for AS28398.1 of 673
Route object: none1.178.72.252/31No route object for it. Add a route object with origin AS28398 in the RIR database for the space.1 of 673
ROA: origin1.178.72.254/31ROAs covering it name AS16509, not AS28398. If AS28398 should announce it, add a ROA for AS28398.1 of 673
Route object: none1.178.72.254/31No route object for it. Add a route object with origin AS28398 in the RIR database for the space.1 of 673
ROA: origin45.68.64.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS28398 should announce it, add a ROA for AS28398.1 of 673
Route object: none45.68.64.0/24Route objects for it name AS0. Add a route object with origin AS28398 in the RIR database for the space.1 of 673
ROA: origin62.115.33.170/31ROAs covering it name AS1299, not AS28398. If AS28398 should announce it, add a ROA for AS28398.1 of 673
Route object: none62.115.33.170/31No route object for it. Add a route object with origin AS28398 in the RIR database for the space.1 of 673
ROA: origin63.220.204.220/30ROAs covering it name AS3491, AS31713, not AS28398. If AS28398 should announce it, add a ROA for AS28398.1 of 673
Route object: none63.220.204.220/30No route object for it. Add a route object with origin AS28398 in the RIR database for the space.1 of 673
ROA: origin64.86.54.44/31ROAs covering it name AS6453, not AS28398. If AS28398 should announce it, add a ROA for AS28398.1 of 673
Route object: none64.86.54.44/31No route object for it. Add a route object with origin AS28398 in the RIR database for the space.1 of 673
ROA: origin71.18.242.16/31ROAs covering it name AS396986, not AS28398. If AS28398 should announce it, add a ROA for AS28398.1 of 673
Route object: none71.18.242.16/31No route object for it. Add a route object with origin AS28398 in the RIR database for the space.1 of 673
ROA: origin72.14.243.168/31ROAs covering it name AS15169, not AS28398. If AS28398 should announce it, add a ROA for AS28398.1 of 673
Route object: none72.14.243.168/31No route object for it. Add a route object with origin AS28398 in the RIR database for the space.1 of 673
ROA: origin79.140.89.156/31ROAs covering it name AS6762, not AS28398. If AS28398 should announce it, add a ROA for AS28398.1 of 673
Route object: none79.140.89.156/31No route object for it. Add a route object with origin AS28398 in the RIR database for the space.1 of 673
ROA: origin94.142.103.190/31ROAs covering it name AS12956, not AS28398. If AS28398 should announce it, add a ROA for AS28398.1 of 673
Route object: none94.142.103.190/31No route object for it. Add a route object with origin AS28398 in the RIR database for the space.1 of 673
ROA: origin128.241.8.20/31ROAs covering it name AS2914, not AS28398. If AS28398 should announce it, add a ROA for AS28398.1 of 673
Route object: none128.241.8.20/31No route object for it. Add a route object with origin AS28398 in the RIR database for the space.1 of 673
ROA: origin138.122.99.152/31ROAs covering it name AS28458, not AS28398. If AS28398 should announce it, add a ROA for AS28398.1 of 673
Route object: none138.122.99.152/31No route object for it. Add a route object with origin AS28398 in the RIR database for the space.1 of 673
ROA: origin184.105.12.224/30ROAs covering it name AS6939, not AS28398. If AS28398 should announce it, add a ROA for AS28398.1 of 673
Route object: none184.105.12.224/30No route object for it. Add a route object with origin AS28398 in the RIR database for the space.1 of 673
ROA: origin200.25.32.96/31ROAs covering it name AS7195, not AS28398. If AS28398 should announce it, add a ROA for AS28398.1 of 673
Route object: none200.25.32.96/31No route object for it. Add a route object with origin AS28398 in the RIR database for the space.1 of 673
ROA: origin206.72.210.0/23An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS28398 should announce it, add a ROA for AS28398.1 of 673
Route object: none206.72.210.0/23No route object for it. Add a route object with origin AS28398 in the RIR database for the space.1 of 673
ROA: origin208.184.124.112/31ROAs covering it name AS6461, not AS28398. If AS28398 should announce it, add a ROA for AS28398.1 of 673
Route object: none208.184.124.112/31No route object for it. Add a route object with origin AS28398 in the RIR database for the space.1 of 673
ROA: maxLength2806:206:0:4000::120/124ROA 2806:206::/32 AS28398 has maxLength 32; the route is a /124. Raise the maxLength, or add a ROA for 2806:206:0:4000::120/124.1 of 636
Route object: none2806:206:0:4000::120/124No route object for it. A route object for 2806:206::/32 with origin AS28398 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS28398 in the RIR database for the space.1 of 636
Bogon prefix0.0.0.0/0In IANA's special-purpose registry: default route.1 of 673
Bogon prefix10.141.141.0/24In IANA's special-purpose registry: Private-Use (RFC 1918).1 of 673
Bogon prefix192.168.19.252/30In IANA's special-purpose registry: Private-Use (RFC 1918).1 of 673
Bogon prefix192.168.20.252/30In IANA's special-purpose registry: Private-Use (RFC 1918).1 of 673
Bogon prefix::/0In IANA's special-purpose registry: default route.1 of 636
ROA: none8.243.210.240/30No ROA covers it. Add a ROA for AS28398, maxLength 30.1 of 673
Route object: none8.243.210.240/30No route object for it. Add a route object with origin AS28398 in the RIR database for the space.1 of 673
ROA: none38.32.254.134/31No ROA covers it. Add a ROA for AS28398, maxLength 31.1 of 673
Route object: none38.32.254.134/31No route object for it. Add a route object with origin AS28398 in the RIR database for the space.1 of 673
ROA: none65.175.54.164/30No ROA covers it. Add a ROA for AS28398, maxLength 30.1 of 673
Route object: none65.175.54.164/30No route object for it. Add a route object with origin AS28398 in the RIR database for the space.1 of 673
ROA: none157.240.92.150/31No ROA covers it. Add a ROA for AS28398, maxLength 31.1 of 673
Route object: none157.240.92.150/31No route object for it. Add a route object with origin AS28398 in the RIR database for the space.1 of 673
Route object: RIR38.7.16.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.7.17.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.7.18.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.7.19.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.7.20.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.7.21.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.7.22.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.7.23.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.141.80.0/20Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.141.80.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.141.81.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.141.82.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.141.83.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.141.84.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.141.85.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.141.86.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.141.87.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.141.88.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.141.89.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.141.90.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.141.91.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.141.92.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.141.93.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.141.94.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.141.95.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR164.163.188.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR164.163.189.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR164.163.190.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR164.163.191.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR206.85.9.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR206.85.10.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR206.85.11.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR206.85.8.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673

Route objects not announced

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

2001:470:3a6::/48ARINValid
2806:2060::/32RADBNo ROA

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.