VizieR

CfA VizieR . ADAC VizieR . Cambridge (UK) VizieR . IUCAA VizieR . INASAN VizieR .

Catalog

Looking for catalogs ..
The VizieR service is now hosted by CDS domain (cds.unistra.fr). Please, modify your configuration for the new domain.
13 catalogs found

ALL
       or   
      
    
J/ApJ/726/16
(c)
102
{gamma}-ray loud blazars (Linford+, 2011)
img(gal)
    
J/ApJ/744/177
(c)
VLBA 5GHz observations of Fermi/LAT AGNs (Linford+, 2012)
img(gal)
    
J/ApJ/748/49
(c)
Optical spectroscopy of 1LAC broad-line blazars (Shaw+, 2012)
img(gal)
    
J/ApJ/810/14
(c)
Third catalog of LAT-detected AGNs (3LAC) (Ackermann+, 2015)
img(gal)
    
J/ApJ/880/32
(c)
Optical/{gamma}-ray flares for Fermi-LAT blazars (Liodakis+, 2019)
timeSerie
img(gal)
    
J/ApJ/925/120
(c)
255
Luminosities & peak frequencies of 4FGL blazars (Yang+, 2022)
img(gal)
    
J/ApJS/260/12
(c)
11k
Jet kinematics of blazars at 43GHz with 10yrs obs. (Weaver+, 2022)
timeSerie
img(gal)
    
J/ApJS/262/18
(c)
2k
Spectral energy distributions for 4FGL blazars (Yang+, 2022)
img(gal)
    
J/ApJS/271/20
(c)
1k
Broad emission line of 4FGL blazars (Chen+, 2024)
img(gal)
    
J/ApJS/279/3
(c)
1k
ZTF LC analysis of Fermi LAT (4LAC-DR3) AGNs (Xiong+, 2025)
img(gal)
    
J/MNRAS/510/469
(c)
331
Radio and {Gamma}-ray of MOJAVE-Fermi AGNs (Kramarenko+, 2022)
timeSerie/pdf
img(gal)
    
J/MNRAS/519/6349
(c)
1k
The gamma/optical flares of 4FGL-DR3 blazars (De Jaeger+, 2023)
img(gal)
    
J/other/Nat/515.376
(c)
217
Power of relativistic jets in blazars (Ghisellini+, 2014)
img(gal)

ALL
       or   
       (c)  indicates tables which contain celestial coordinates 


The following problems were encountered in this VizieR run:
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_conn_dbms,     Status: STDB_ERR 
****No server is available for connection
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****db1_relink(0): connection was not opened
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_conn_dbms,     Status: STDB_ERR 
****No server is available for connection
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****db1_relink(0): connection was not opened
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_conn_dbms,     Status: STDB_ERR 
****No server is available for connection
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****db1_relink(0): connection was not opened
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_conn_dbms,     Status: STDB_ERR 
****No server is available for connection
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****db1_relink(0): connection was not opened
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_conn_dbms,     Status: STDB_ERR 
****No server is available for connection
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
If you can't find a solution, report to CDS and insert into your message the following details:

.errorfile=/tmp/VR3666475.err (2026-08-11T20:17:33)
-2
-kw.cat=1038051501
-ref=VIZ6a7b835e37f22b
elapse time 1

Cite/acknowledge VizieR catalogue
Rules of usage of VizieR data

© UDS/CNRS

Contact