bgpreport

Network · data from 2026-11-12

AS269138 MOV TELECOM

Registry name: AS269138 - MOV TELECOM SERVICOS DE PROVEDORES DE INTERNET LTD, BR · PeeringDB

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

Announced routes

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

45.180.148.0/23 No ROA Nonecovered by 45.180.148.0/22 671 100% 66
45.180.150.0/23 No ROA Nonecovered by 45.180.148.0/22 671 100% 66
2804:5ffc::/33 No ROA Nonecovered by 2804:5ffc::/32 635 100% 67
2804:5ffc:8000::/33 No ROA Nonecovered by 2804:5ffc::/32 635 100% 67
2804:5ffc::/34 No ROA Nonecovered by 2804:5ffc::/32 349 55% 64
2804:5ffc:4000::/34 No ROA Nonecovered by 2804:5ffc::/32 349 55% 64
2804:5ffc:8000::/34 No ROA Nonecovered by 2804:5ffc::/32 349 55% 64
2804:5ffc:c000::/34 No ROA Nonecovered by 2804:5ffc::/32 349 55% 64
45.180.151.0/24 No ROA Nonecovered by 45.180.148.0/22 203 30% 54
45.180.148.0/24 No ROA Nonecovered by 45.180.148.0/22 202 30% 54
45.180.149.0/24 No ROA Nonecovered by 45.180.148.0/22 202 30% 54
45.180.150.0/24 No ROA Nonecovered by 45.180.148.0/22 202 30% 54
45.180.148.0/22 No ROA Other IRR onlyRADB, TC 672 100% 66
2804:5ffc::/32 No ROA Other IRR onlyRADB, TC 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS269138: AS269138:AS-ALL. 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 (AS269138 isn't in the set, or no route object for AS269138 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 objectsAS269138 in itNot covered
AS269138:AS-ALL TC 122 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 28 are in fix.csv.

  • ROA: none14
  • Route object: none12
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none45.180.148.0/23No ROA covers it. Add a ROA for AS269138, maxLength 23.671 of 673
Route object: none45.180.148.0/23No route object for it. A route object for 45.180.148.0/22 with origin AS269138 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269138 in the RIR database for the space.671 of 673
ROA: none45.180.150.0/23No ROA covers it. Add a ROA for AS269138, maxLength 23.671 of 673
Route object: none45.180.150.0/23No route object for it. A route object for 45.180.148.0/22 with origin AS269138 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269138 in the RIR database for the space.671 of 673
ROA: none2804:5ffc::/33No ROA covers it. Add a ROA for AS269138, maxLength 33.635 of 636
Route object: none2804:5ffc::/33No route object for it. A route object for 2804:5ffc::/32 with origin AS269138 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269138 in the RIR database for the space.635 of 636
ROA: none2804:5ffc:8000::/33No ROA covers it. Add a ROA for AS269138, maxLength 33.635 of 636
Route object: none2804:5ffc:8000::/33No route object for it. A route object for 2804:5ffc::/32 with origin AS269138 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269138 in the RIR database for the space.635 of 636
ROA: none2804:5ffc::/34No ROA covers it. Add a ROA for AS269138, maxLength 34.349 of 636
Route object: none2804:5ffc::/34No route object for it. A route object for 2804:5ffc::/32 with origin AS269138 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269138 in the RIR database for the space.349 of 636
ROA: none2804:5ffc:4000::/34No ROA covers it. Add a ROA for AS269138, maxLength 34.349 of 636
Route object: none2804:5ffc:4000::/34No route object for it. A route object for 2804:5ffc::/32 with origin AS269138 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269138 in the RIR database for the space.349 of 636
ROA: none2804:5ffc:8000::/34No ROA covers it. Add a ROA for AS269138, maxLength 34.349 of 636
Route object: none2804:5ffc:8000::/34No route object for it. A route object for 2804:5ffc::/32 with origin AS269138 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269138 in the RIR database for the space.349 of 636
ROA: none2804:5ffc:c000::/34No ROA covers it. Add a ROA for AS269138, maxLength 34.349 of 636
Route object: none2804:5ffc:c000::/34No route object for it. A route object for 2804:5ffc::/32 with origin AS269138 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269138 in the RIR database for the space.349 of 636
ROA: none45.180.151.0/24No ROA covers it. Add a ROA for AS269138, maxLength 24.203 of 673
Route object: none45.180.151.0/24No route object for it. A route object for 45.180.148.0/22 with origin AS269138 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269138 in the RIR database for the space.203 of 673
ROA: none45.180.148.0/24No ROA covers it. Add a ROA for AS269138, maxLength 24.202 of 673
Route object: none45.180.148.0/24No route object for it. A route object for 45.180.148.0/22 with origin AS269138 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269138 in the RIR database for the space.202 of 673
ROA: none45.180.149.0/24No ROA covers it. Add a ROA for AS269138, maxLength 24.202 of 673
Route object: none45.180.149.0/24No route object for it. A route object for 45.180.148.0/22 with origin AS269138 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269138 in the RIR database for the space.202 of 673
ROA: none45.180.150.0/24No ROA covers it. Add a ROA for AS269138, maxLength 24.202 of 673
Route object: none45.180.150.0/24No route object for it. A route object for 45.180.148.0/22 with origin AS269138 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269138 in the RIR database for the space.202 of 673
ROA: none45.180.148.0/22No ROA covers it. Add a ROA for AS269138, maxLength 22.672 of 673
Route object: RIR45.180.148.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none2804:5ffc::/32No ROA covers it. Add a ROA for AS269138, maxLength 32.635 of 636
Route object: RIR2804:5ffc::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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